New translation batch for cn (#31650)
This commit is contained in:
docubot
@@ -234,6 +234,7 @@ translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifi
|
||||
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md,broken liquid tags
|
||||
@@ -295,6 +296,7 @@ translations/zh-CN/content/admin/configuration/configuring-your-enterprise/confi
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error
|
||||
@@ -305,6 +307,7 @@ translations/zh-CN/content/admin/identity-and-access-management/using-enterprise
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags
|
||||
@@ -482,6 +485,7 @@ translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-y
|
||||
translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md,broken liquid tags
|
||||
translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error
|
||||
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/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,rendering error
|
||||
translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md,rendering error
|
||||
@@ -526,7 +530,7 @@ translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md,rendering error
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,rendering error
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error
|
||||
translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error
|
||||
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
|
||||
|
||||
|
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 个性化您的个人资料
|
||||
intro: '你可以在个人资料中设置头像和添加个人简历，与其他 {% data variables.product.product_name %} 用户共享你自己的信息。'
|
||||
title: Personalizing your profile
|
||||
intro: 'You can share information about yourself with other {% data variables.product.product_name %} users by setting a profile picture and adding a bio to your profile.'
|
||||
redirect_from:
|
||||
- /articles/adding-a-bio-to-your-profile
|
||||
- /articles/setting-your-profile-picture
|
||||
@@ -18,156 +18,186 @@ versions:
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Personalize
|
||||
ms.openlocfilehash: c12fccd91144428fe9aad2f01d2c0b0941fdd4d4
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146681051'
|
||||
---
|
||||
## 更改头像
|
||||
## Changing your profile picture
|
||||
|
||||
您的头像可帮助在 {% data variables.product.product_name %} 的拉取请求、评论、参与页面及图形中识别您。
|
||||
Your profile picture helps identify you across {% data variables.product.product_name %} in pull requests, comments, contributions pages, and graphs.
|
||||
|
||||
在注册帐户时，{% data variables.product.product_name %} 会提供一个随机生成的“默认肖像”。 [哈希头像](https://github.com/blog/1586-identicons)根据用户 ID 的哈希生成，因此无法控制其颜色或模式。 您可以将默认肖像替换为能代表您的图片。
|
||||
When you sign up for an account, {% data variables.product.product_name %} provides you with a randomly generated "identicon". [Your identicon](https://github.com/blog/1586-identicons) generates from a hash of your user ID, so there's no way to control its color or pattern. You can replace your identicon with an image that represents you.
|
||||
|
||||
{% note %}
|
||||
|
||||
注意{% ifversion ghec %}s{% endif %}：{% ifversion ghec %}
|
||||
**Note{% ifversion ghec %}s{% endif %}**: {% ifversion ghec %}
|
||||
|
||||
* {% endif %}个人资料图片应为 PNG、JPG 或 GIF 文件，其大小必须小于 1 MB，且小于 3000 x 3000 像素。 为获取质量最佳的渲染，建议图像的像素保持在大约 500 x 500 像素。
|
||||
{% ifversion ghec %}* {% data variables.product.prodname_emus %} 不支持 Gravatar 头像。{% endif %}
|
||||
* {% endif %}Your profile picture should be a PNG, JPG, or GIF file, and it must be less than 1 MB in size and smaller than 3000 by 3000 pixels. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels.
|
||||
{% ifversion ghec %}* Gravatar profile pictures are not supported with {% data variables.product.prodname_emus %}.{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### 设置头像
|
||||
### Setting a profile picture
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
2. 在“个人资料图片”下，单击 {% octicon "pencil" aria-label="The edit icon" %}“编辑” 。
|
||||
|
||||
3. 单击“上传照片...”。{% ifversion not ghae %}{% endif %}
|
||||
3. 裁剪图片。 完成后，单击“设置新的个人资料图片”。
|
||||
|
||||
2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
|
||||
|
||||
3. Click **Upload a photo...**.{% ifversion not ghae %}
|
||||
{% endif %}
|
||||
3. Crop your picture. When you're done, click **Set new profile picture**.
|
||||
|
||||
|
||||
### 将头像重置为默认肖像
|
||||
### Resetting your profile picture to the identicon
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
2. 在“个人资料图片”下，单击 {% octicon "pencil" aria-label="The edit icon" %}“编辑” 。
|
||||
|
||||
3. 要还原为哈希头像，请单击“删除照片”。 {% ifversion not ghae %}如果电子邮件地址与 [Gravatar](https://en.gravatar.com/) 相关联，则无法还原为默认肖像。 此时请单击“还原为 Gravatar”。
|
||||
{% endif %}
|
||||
2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
|
||||
|
||||
3. To revert to your identicon, click **Remove photo**. {% ifversion not ghae %}If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Click **Revert to Gravatar** instead.
|
||||
{% endif %}
|
||||
|
||||
## 更改个人资料名称
|
||||
## Changing your profile name
|
||||
|
||||
您可以更改显示在个人资料中的名称。 此名称也可能显示在您对于组织拥有的私有仓库所做的注释旁边。 有关详细信息，请参阅“[管理组织中成员名称的显示](/articles/managing-the-display-of-member-names-in-your-organization)”。
|
||||
You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "[Managing the display of member names in your organization](/articles/managing-the-display-of-member-names-in-your-organization)."
|
||||
|
||||
{% ifversion fpt or ghec %} {% note %}
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
注意：如果你是 {% data variables.product.prodname_emu_enterprise %} 的成员，则必须通过你的标识提供者而不是 {% data variables.product.prodname_dotcom_the_website %} 对个人资料名称进行任何更改。 {% data reusables.enterprise-accounts.emu-more-info-account %}
|
||||
**Note:** If you're a member of an {% data variables.product.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %}
|
||||
|
||||
{% endnote %} {% endif %}
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
2. 在“Name（名称）”下，键入要显示在个人资料中的名称。
|
||||
|
||||
2. Under "Name", type the name you want to be displayed on your profile.
|
||||
|
||||
|
||||
## 在个人资料中添加个人简历
|
||||
## Adding a bio to your profile
|
||||
|
||||
在个人资料中添加个人简历，与其他 {% data variables.product.product_name %} 用户共享您自己的信息。 借助 [@mentions](/articles/basic-writing-and-formatting-syntax) 和表情符号，你可以在简历中包括以下信息：目前或以前工作的工作地点、从事的工作类型，甚至是喜欢的咖啡种类。
|
||||
Add a bio to your profile to share information about yourself with other {% data variables.product.product_name %} users. With the help of [@mentions](/articles/basic-writing-and-formatting-syntax) and emoji, you can include information about where you currently or have previously worked, what type of work you do, or even what kind of coffee you drink.
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
要以更长和更突出的方式显示有关自己的自定义信息，您还可以使用个人资料自述文件。 有关详细信息，请参阅“[管理个人资料 README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)”。
|
||||
For a longer-form and more prominent way of displaying customized information about yourself, you can also use a profile README. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
注意：如果你为个人资料启用了活动概述部分，并且在个人资料的个人简历中 @mention 你所属的组织，那么该组织将首先出现在你的活动概述中。 有关详细信息，请参阅“[在个人资料中显示活动概述](/articles/showing-an-overview-of-your-activity-on-your-profile)”。
|
||||
**Note:**
|
||||
If you have the activity overview section enabled for your profile and you @mention an organization you're a member of in your profile bio, then that organization will be featured first in your activity overview. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
2. 在“个人简历”下，添加要在个人资料中显示的内容。 个人资料字段限于 160 个字符。
|
||||
|
||||
2. Under **Bio**, add the content that you want displayed on your profile. The bio field is limited to 160 characters.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
提示：当你 @mention 组织时，只有你所属的组织才会自动填写。 你也可 @mention 不是其成员的组织（例如前雇主），但该组织名称不会自动填写。
|
||||
**Tip:** When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
3. 单击“更新个人资料”。
|
||||
|
||||
{% data reusables.profile.update-profile %}
|
||||
|
||||
## 设置状态
|
||||
{% ifversion profile-time-zone %}
|
||||
|
||||
您可以设置状态以显示您当前在 {% data variables.product.product_name %} 上的可用性。 您的状态将会显示：
|
||||
- 在您的 {% data variables.product.product_name %} 个人资料页面上。
|
||||
- 当有人在 {% data variables.product.product_name %} 上将鼠标放在您的用户名或头像上时。
|
||||
- 在您属于其成员的团队页面上时。 有关详细信息，请参阅“[关于团队](/articles/about-teams/#team-pages)”。
|
||||
- 在您属于其成员的组织的组织仪表板上。 有关详细信息，请参阅“[关于组织仪表板](/articles/about-your-organization-dashboard/)”。
|
||||
## Setting your location and time zone
|
||||
|
||||
在设置状态时，您也可以让人们知道您在 {% data variables.product.product_name %} 上的可用性有限。
|
||||
You can set a location and time zone on your profile to show other people your local time. Your location and time zone will be visible:
|
||||
- on your {% data variables.product.product_name %} profile page.
|
||||
- when people hover over your username or avatar on {% data variables.product.product_name %}.
|
||||
|
||||
|
||||
When you view your profile, you will see your location, local time, and your time zone in relation to Universal Time Coordinated.
|
||||
|
||||
|
||||
|
||||
|
||||
如果选择“忙碌”选项，当人们 @mention 你的用户名、分配给你问题或拉取请求或者请求你对拉取请求进行评审时，你的用户名旁边将会出现一条表示你在忙碌的注释。 您还将被排除在分配给您所属的任何团队的拉取请求的自动审核任务之外。 有关详细信息，请参阅“[管理团队的代码评审设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)”。
|
||||
When others view your profile, they will see your location, local time, and the time difference in hours from their own local time.
|
||||
|
||||
1. 在 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %} 的右上角，单击你的个人资料照片，然后单击“设置状态”，或者，如果已设置状态，则单击当前状态。
|
||||
|
||||
2. 要添加自定义文本到状态，请单击文本字段，然后输入状态消息。
|
||||
|
||||
3. （可选）要设置表情符号状态，请单击笑脸图标并从列表中选择表情符号。
|
||||
|
||||
4. （可选）如果想表示您的可用性受限，请选择“Busy（忙碌）”。
|
||||
|
||||
5. 使用“清除状态”下拉菜单，选择状态的到期时间。 如果不选择状态到期时间，您的状态将保持到您清除或编辑状态为止。
|
||||
|
||||
6. 使用下拉菜单，单击您要向其显示状态的组织。 如果不选择组织，您的状态将是公共的。
|
||||
|
||||
7. 单击“设置状态”。
|
||||
|
||||
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
1. Under **Location**, type the location you want to be displayed on your profile.
|
||||
|
||||
|
||||
|
||||
1. Optionally, to display the current local time on your profile, select **Display current local time**.
|
||||
|
||||
|
||||
|
||||
- Select the **Time zone** dropdown menu, then click your local time zone.
|
||||
|
||||
|
||||
|
||||
{% data reusables.profile.update-profile %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Setting a status
|
||||
|
||||
You can set a status to display information about your current availability on {% data variables.product.product_name %}. Your status will show:
|
||||
- on your {% data variables.product.product_name %} profile page.
|
||||
- when people hover over your username or avatar on {% data variables.product.product_name %}.
|
||||
- on a team page for a team where you're a team member. For more information, see "[About teams](/articles/about-teams/#team-pages)."
|
||||
- on the organization dashboard in an organization where you're a member. For more information, see "[About your organization dashboard](/articles/about-your-organization-dashboard/)."
|
||||
|
||||
When you set your status, you can also let people know that you have limited availability on {% data variables.product.product_name %}.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
If you select the "Busy" option, when people @mention your username, assign you an issue or pull request, or request a pull request review from you, a note next to your username will show that you're busy. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
|
||||
|
||||
1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set your status** or, if you already have a status set, click your current status.
|
||||
|
||||
2. To add custom text to your status, click in the text field and type a status message.
|
||||
|
||||
3. Optionally, to set an emoji status, click the smiley icon and select an emoji from the list.
|
||||
|
||||
4. Optionally, if you'd like to share that you have limited availability, select "Busy."
|
||||
|
||||
5. Use the **Clear status** drop-down menu, and select when you want your status to expire. If you don't select a status expiration, you will keep your status until you clear or edit your status.
|
||||
|
||||
6. Use the drop-down menu and click the organization you want your status visible to. If you don't select an organization, your status will be public.
|
||||
|
||||
7. Click **Set status**.
|
||||
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## 在个人资料中显示徽章
|
||||
## Displaying badges on your profile
|
||||
|
||||
当您参与某些计划时， {% data variables.product.prodname_dotcom %} 会自动在您的个人资料中显示徽章。
|
||||
When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile.
|
||||
|
||||
| 徽章 | 节目 | 说明 |
|
||||
| Badge | Program | Description |
|
||||
| --- | --- | --- |
|
||||
| {% octicon "cpu" aria-label="The Developer Program icon" %} | **开发人员计划成员** | 如果您是 {% data variables.product.prodname_dotcom %} 开发者计划的注册成员，使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 构建应用程序，您的个人资料上将获得开发者计划成员徽章。 有关 {% data variables.product.prodname_dotcom %} 开发人员计划的更多信息，请参阅 [GitHub 开发人员](/program/)。 |
|
||||
| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | 如果您使用 {% data variables.product.prodname_pro %}，您的个人资料中将获得一个 PRO 徽章。 有关 {% data variables.product.prodname_pro %} 的详细信息，请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/github/getting-started-with-github/githubs-products#github-pro)”。 |
|
||||
| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | 如果你帮助寻找安全漏洞，您的个人资料上将获得 Security Bug Bounty Hunter 徽章。 有关 {% data variables.product.prodname_dotcom %} 安全计划的详细信息，请参阅 [{% data variables.product.prodname_dotcom %} 安全性](https://bounty.github.com/)。 |
|
||||
| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} 校园专家** | 如果您参加 {% data variables.product.prodname_campus_program %}，您的个人资料上将获得 {% data variables.product.prodname_dotcom %} 校园专家徽章。 有关校园专家计划的详细信息，请参阅[校园专家](https://education.github.com/experts)。 |
|
||||
| {% octicon "shield" aria-label="The shield icon" %} | 安全公告信用 | 如果你提交到 [{% data variables.product.prodname_dotcom %} 公告数据库](https://github.com/advisories)的安全公告被接受，你的个人资料上将获得一个安全公告信用徽章。 有关 {% data variables.product.prodname_dotcom %} 安全公告的详细信息，请参阅“[{% data variables.product.prodname_dotcom %} 安全公告](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)”。 |
|
||||
| {% octicon "check" aria-label="The check icon" %} | 已回答的讨论 | 如果对讨论的答复标记为答案，你将在个人资料上获得“已回答的讨论”徽章。 有关 {% data variables.product.prodname_dotcom %} 的详细信息，请参阅[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)。 |
|
||||
| {% octicon "cpu" aria-label="The Developer Program icon" %} | **Developer Program Member** | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/). |
|
||||
| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. For more information about {% data variables.product.prodname_pro %}, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products#github-pro)." |
|
||||
| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/). |
|
||||
| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} Campus Expert** | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts). |
|
||||
| {% octicon "shield" aria-label="The shield icon" %} | **Security advisory credit** | If a security advisory you submit to the [{% data variables.product.prodname_dotcom %} Advisory Database](https://github.com/advisories) is accepted, you'll get a Security advisory credit badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Security Advisories, see [{% data variables.product.prodname_dotcom %} Security Advisories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories). |
|
||||
| {% octicon "check" aria-label="The check icon" %} | **Discussion answered** | If your reply to a discussion is marked as the answer, you'll get a Discussion answered badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Discussions, see [About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions). |
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## 获得成就
|
||||
## Earning Achievements
|
||||
|
||||
成就庆祝 {% data variables.product.prodname_dotcom %} 上发生的特定事件和操作。 它们将显示为你的个人资料边栏中列出的小徽章。 单击或悬停在成就上将显示一个详细视图，该视图提示如何获得成就，并提供简短说明和参与事件的链接。 事件链接将仅对有权访问发生事件的存储库或组织的用户可见。 对于没有访问权限的所有用户，事件链接将不可访问。
|
||||
Achievements celebrate specific events and actions that happen on {% data variables.product.prodname_dotcom %}. They will appear as small badges listed in the sidebar of your profile. Clicking or hovering on an achievement will show a detailed view that hints at how the achievement was earned, with a short description and links to the contributing events. The event links will only be visible to users that have access to the repository or organization that the event took place in. Event links will appear inaccessible to all users without access.
|
||||
|
||||
若要阻止私人贡献计入成就，或完全关闭成就，请参阅“[在个人资料上显示你的私人贡献和成就](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)”。
|
||||
To stop private contributions from counting toward your Achievements, or to turn off Achievements entirely, see "[Showing your private contributions and Achievements on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
|
||||
|
||||
{% note %}
|
||||
|
||||
注意：此功能目前为 beta 版本，可能会有变动。
|
||||
**Note:** This feature is currently in beta and subject to change.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Mars 2020 Helicopter 贡献者成就的合格仓库列表
|
||||
## List of qualifying repositories for Mars 2020 Helicopter Contributor achievement
|
||||
|
||||
如果你为下面一个或多个仓库列出的标记撰写了提交历史记录中的任何提交，你的个人资料中将获得 Mars 2020 Helicopter 贡献者成就。 撰写的提交必须有验证过的电子邮件地址，该电子邮件地址在 {% data variables.product.prodname_dotcom %} 确定符合条件的贡献时与您帐户关联，表示该贡献归属于您。 你可以是提交的原始作者或[共同作者之一](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)。 将来对经过验证的电子邮件的更改不会对徽章产生影响。 我们根据从美国航天局喷气推进实验室获得的资料编制了清单。
|
||||
If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor achievement on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. You can be the original author or [one of the co-authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) of the commit. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
|
||||
|
||||
| {% data variables.product.prodname_dotcom %} 仓库 | 版本 | 标记 |
|
||||
| {% data variables.product.prodname_dotcom %} Repository | Version | Tag |
|
||||
|---|---|---|
|
||||
| [torvalds/linux](https://github.com/torvalds/linux) | 3.4 | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4) |
|
||||
| [python/cpython](https://github.com/python/cpython) | 3.9.2 | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2) |
|
||||
@@ -238,6 +268,6 @@ ms.locfileid: '146681051'
|
||||
| [locationtech/jts](https://github.com/locationtech/jts) | 1.15.0 | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0) |
|
||||
| [apache/logging-log4j2](https://github.com/apache/logging-log4j2) | 2.11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) |
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- [关于个人资料](/articles/about-your-profile)
|
||||
- "[About your profile](/articles/about-your-profile)"
|
||||
|
||||
@@ -275,7 +275,7 @@ This list describes the recommended approaches for accessing repository data wit
|
||||
|
||||
{% ifversion fpt or ghec %}**Self-hosted**{% elsif ghes or ghae %}Self-hosted{% endif %} runners for {% data variables.product.product_name %} do not have guarantees around running in ephemeral clean virtual machines, and can be persistently compromised by untrusted code in a workflow.
|
||||
|
||||
{% ifversion fpt or ghec %}As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal repositories, as anyone who can fork the repository and open a pull request (generally those with read access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which, depending on its settings, can grant write access to the repository. Although workflows can control access to environment secrets by using environments and required reviews, these workflows are not run in an isolated environment and are still susceptible to the same risks when run on a self-hosted runner.
|
||||
{% ifversion fpt or ghec %}As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal repositories, as anyone who can fork the repository and open a pull request (generally those with read access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which, depending on its settings, can grant write access to the repository. Although workflows can control access to environment secrets by using environments and required reviews, these workflows are not run in an isolated environment and are still susceptible to the same risks when run on a self-hosted runner.
|
||||
|
||||
When a self-hosted runner is defined at the organization or enterprise level, {% data variables.product.product_name %} can schedule workflows from multiple repositories onto the same runner. Consequently, a security compromise of these environments can result in a wide impact. To help reduce the scope of a compromise, you can create boundaries by organizing your self-hosted runners into separate groups. You can restrict what {% ifversion restrict-groups-to-workflows %}workflows, {% endif %}organizations and repositories can access runner groups. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: 在启用 GitHub Actions 的情况下备份和恢复 GitHub Enterprise Server
|
||||
title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled
|
||||
shortTitle: Backing up and restoring
|
||||
intro: '外部存储提供程序上的 {% data variables.product.prodname_actions %} 数据不会包含在常规 {% data variables.product.prodname_ghe_server %} 备份中，必须单独备份。'
|
||||
intro: 'To restore a backup of {% data variables.product.product_location %} when {% data variables.product.prodname_actions %} is enabled, you must configure {% data variables.product.prodname_actions %} before restoring the backup with {% data variables.product.prodname_enterprise_backup_utilities %}.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
type: how_to
|
||||
@@ -12,50 +12,33 @@ topics:
|
||||
- Infrastructure
|
||||
redirect_from:
|
||||
- /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
|
||||
ms.openlocfilehash: def12b4e9e93a75ee1aa58f8290ca1b6e7d13cd5
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145100008'
|
||||
---
|
||||
{% data reusables.actions.enterprise-storage-ha-backups %}
|
||||
|
||||
如果您使用 {% data variables.product.prodname_enterprise_backup_utilities %} 来备份 {% data variables.product.product_location %}，请务必注意，存储在外部存储提供程序上的 {% data variables.product.prodname_actions %} 数据不会包含在备份中。
|
||||
## About backups of {% data variables.product.product_name %} when using {% data variables.product.prodname_actions %}
|
||||
|
||||
以下是将带有 {% data variables.product.prodname_actions %} 的 {% data variables.product.product_location %} 恢复到新设备所需步骤的概述：
|
||||
You can use {% data variables.product.prodname_enterprise_backup_utilities %} to back up and restore the data and configuration for {% data variables.product.product_location %} to a new instance. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)."
|
||||
|
||||
1. 确认原始设备处于脱机状态。
|
||||
1. 在替换 {% data variables.product.prodname_ghe_server %} 设备上手动配置网络设置。 网络设置被排除在备份快照之外，不会被 `ghe-restore` 覆盖。
|
||||
1. 若要将替换设备配置为使用与原始设备相同的 {% data variables.product.prodname_actions %} 外部存储配置，请从新设备使用 `ghe-config` 命令设置所需的参数。
|
||||
|
||||
- Azure Blob 存储
|
||||
```shell
|
||||
ghe-config secrets.actions.storage.blob-provider "azure"
|
||||
ghe-config secrets.actions.storage.azure.connection-string "_Connection_String_"
|
||||
```
|
||||
- Amazon S3
|
||||
```shell
|
||||
ghe-config secrets.actions.storage.blob-provider "s3"
|
||||
ghe-config secrets.actions.storage.s3.bucket-name "_S3_Bucket_Name"
|
||||
ghe-config secrets.actions.storage.s3.service-url "_S3_Service_URL_"
|
||||
ghe-config secrets.actions.storage.s3.access-key-id "_S3_Access_Key_ID_"
|
||||
ghe-config secrets.actions.storage.s3.access-secret "_S3_Access_Secret_"
|
||||
```
|
||||
- （可选）要启用 S3 强制路径样式，请输入以下命令：
|
||||
```shell
|
||||
ghe-config secrets.actions.storage.s3.force-path-style true
|
||||
```
|
||||
|
||||
However, not all the data for {% data variables.product.prodname_actions %} is included in these backups. {% data reusables.actions.enterprise-storage-ha-backups %}
|
||||
|
||||
1. 在替换设备上启用 {% data variables.product.prodname_actions %}。 这将把替换设备连接到 {% data variables.product.prodname_actions %} 的相同外部存储。
|
||||
## Restoring a backup of {% data variables.product.product_name %} when {% data variables.product.prodname_actions %} is enabled
|
||||
|
||||
```shell
|
||||
ghe-config app.actions.enabled true
|
||||
ghe-config-apply
|
||||
```
|
||||
To restore a backup of {% data variables.product.product_location %} with {% data variables.product.prodname_actions %}, you must manually configure network settings and external storage on the destination instance before you restore your backup from {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
|
||||
1. 配置并启用 {% data variables.product.prodname_actions %} 后，使用 `ghe-restore` 命令从备份中还原其余数据。 有关详细信息，请参阅“[还原备份](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)”。
|
||||
1. 在替换设备上重新注册自托管运行器。 有关详细信息，请参阅[添加自托管运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)。
|
||||
1. Confirm that the source instance is offline.
|
||||
1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} instance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
|
||||
1. SSH into the destination instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
|
||||
|
||||
有关备份和还原 {% data variables.product.prodname_ghe_server %} 的详细信息，请参阅“[在设备上配置备份](/admin/configuration/configuring-backups-on-your-appliance)”。
|
||||
```shell{:copy}
|
||||
$ ssh -p 122 admin@HOSTNAME
|
||||
```
|
||||
1. Configure the destination instance to use the same external storage service for {% data variables.product.prodname_actions %} as the source instance by entering one of the following commands.
|
||||
{% indented_data_reference reusables.actions.configure-storage-provider-platform-commands spaces=3 %}
|
||||
{% data reusables.actions.configure-storage-provider %}
|
||||
1. To prepare to enable {% data variables.product.prodname_actions %} on the destination instance, enter the following command.
|
||||
|
||||
```shell{:copy}
|
||||
ghe-config app.actions.enabled true
|
||||
```
|
||||
{% data reusables.actions.apply-configuration-and-enable %}
|
||||
1. After {% data variables.product.prodname_actions %} is configured and enabled, to restore the rest of the data from the backup, use the `ghe-restore` command. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)."
|
||||
1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
|
||||
|
||||
@@ -1,53 +1,157 @@
|
||||
---
|
||||
title: 设置暂存实例
|
||||
intro: '可在单独的隔离环境中设置 {% data variables.product.product_name %} 实例，并使用该实例来验证和测试更改。'
|
||||
title: Setting up a staging instance
|
||||
intro: 'You can set up a {% data variables.product.product_name %} instance in a separate, isolated environment, and use the instance to validate and test changes.'
|
||||
redirect_from:
|
||||
- /enterprise/admin/installation/setting-up-a-staging-instance
|
||||
- /admin/installation/setting-up-a-staging-instance
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghes: "*"
|
||||
type: how_to
|
||||
topics:
|
||||
- Enterprise
|
||||
- Infrastructure
|
||||
- Upgrades
|
||||
shortTitle: Set up a staging instance
|
||||
ms.openlocfilehash: 86006b3dd1fcdd7a7139f35934cafce1f208c8bb
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147065360'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
---
|
||||
## 关于暂存实例
|
||||
|
||||
{% data variables.product.company_short %} 建议将单独的环境设置为测试对 {% data variables.product.product_location %} 的配置的备份、更新或更改。 此环境应与生产系统隔离，称为过渡环境。
|
||||
## About staging instances
|
||||
|
||||
例如，为了防止数据丢失，可以定期验证生产实例的备份。 可以定期在过渡环境中将生产数据的备份还原到单独的 {% data variables.product.product_name %} 实例。 在此暂存实例上，还可以测试是否升级到 {% data variables.product.product_name %} 的最新功能版。
|
||||
{% data variables.product.company_short %} recommends that you set up a separate environment to test backups, updates, or changes to the configuration for {% data variables.product.product_location %}. This environment, which you should isolate from your production systems, is called a staging environment.
|
||||
|
||||
For example, to protect against loss of data, you can regularly validate the backup of your production instance. You can regularly restore the backup of your production data to a separate {% data variables.product.product_name %} instance in a staging environment. On this staging instance, you could also test the upgrade to the latest feature release of {% data variables.product.product_name %}.
|
||||
|
||||
{% tip %}
|
||||
|
||||
提示：只要暂存实例未用于生产容量，便可以重复使用现有 {% data variables.product.prodname_enterprise %} 许可证文件。
|
||||
**Tip:** You may reuse your existing {% data variables.product.prodname_enterprise %} license file as long as the staging instance is not used in a production capacity.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 过渡环境的注意事项
|
||||
## Considerations for a staging environment
|
||||
|
||||
若要完全测试 {% data variables.product.product_name %} 并尽可能重新创建与生产环境类似的环境，请考虑与实例交互的外部系统。 例如，你可能想要在过渡环境中测试以下内容。
|
||||
To thoroughly test {% data variables.product.product_name %} and recreate an environment that's as similar to your production environment as possible, consider the external systems that interact with your instance. For example, you may want to test the following in your staging environment.
|
||||
|
||||
- 身份验证，特别是在使用外部身份验证提供程序（如 SAML）的情况下
|
||||
- 与外部事件单记录系统的集成
|
||||
- 与持续集成服务器的集成
|
||||
- 使用 {% data variables.product.prodname_enterprise_api %} 的外部脚本或软件
|
||||
- 用于发送电子邮件通知的外部 SMTP 服务器
|
||||
- Authentication, especially if you use an external authentication provider like SAML
|
||||
- Integration with an external ticketing system
|
||||
- Integration with a continuous integration server
|
||||
- External scripts or software that use the {% data variables.product.prodname_enterprise_api %}
|
||||
- External SMTP server for email notifications
|
||||
|
||||
## 设置暂存实例
|
||||
## Setting up a staging instance
|
||||
|
||||
1. 使用 {% data variables.product.prodname_enterprise_backup_utilities %} 执行生产实例备份。 有关详细信息，请参阅“[在设备上配置备份](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#about-github-enterprise-server-backup-utilities)”的“关于 {% data variables.product.prodname_enterprise_backup_utilities %}”部分。
|
||||
2. 设置新实例作为暂存环境。 配置和安装暂存实例的方法与生产实例所用方法相同。 有关详细信息，请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)”。
|
||||
3. （可选）如果计划在测试环境中测试 {% data variables.product.prodname_actions %} 功能，请查看日志和存储的注意事项。 有关详细信息，请参阅“[使用过渡环境](/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment)”。
|
||||
4. 在暂存实例上还原备份。 有关详细信息，请参阅“[在设备上配置备份](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#restoring-a-backup)”的“还原备份”部分。
|
||||
You can set up a staging instance from scratch and configure the instance however you like. For more information, see "[Setting up a {% data variables.product.product_name %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)" and "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
|
||||
|
||||
## 延伸阅读
|
||||
Alternatively, you can create a staging instance that reflects your production configuration by restoring a backup of your production instance to the staging instance.
|
||||
|
||||
- “[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)”
|
||||
1. [Back up your production instance](#1-back-up-your-production-instance).
|
||||
2. [Set up a staging instance](#2-set-up-a-staging-instance).
|
||||
3. [Configure {% data variables.product.prodname_actions %}](#3-configure-github-actions).
|
||||
4. [Configure {% data variables.product.prodname_registry %}](#4-configure-github-packages).
|
||||
5. [Restore your production backup](#5-restore-your-production-backup).
|
||||
6. [Review the instance's configuration](#6-review-the-instances-configuration).
|
||||
7. [Apply the instance's configuration](#7-apply-the-instances-configuration).
|
||||
|
||||
### 1. Back up your production instance
|
||||
|
||||
If you want to test changes on an instance that contains the same data and configuration as your production instance, back up the data and configuration from the production instance using {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you use {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} in production, your backup will include your production configuration for external storage. To avoid potential loss of data by writing to your production storage from your staging instance, you must configure each feature in steps 3 and 4 before you restore your backup.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### 2. Set up a staging instance
|
||||
|
||||
Set up a new instance to act as your staging environment. You can use the same guides for provisioning and installing your staging instance as you did for your production instance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)."
|
||||
|
||||
If you plan to restore a backup of your production instance, continue to the next step. Alternatively, you can configure the instance manually and skip the following steps.
|
||||
|
||||
### 3. Configure {% data variables.product.prodname_actions %}
|
||||
|
||||
Optionally, if you use {% data variables.product.prodname_actions %} on your production instance, configure the feature on the staging instance before restoring your production backup. If you don't use {% data variables.product.prodname_actions %}, skip to "[4. Configure {% data variables.product.prodname_registry %}](#4-configure-github-packages)."
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you don't configure {% data variables.product.prodname_actions %} on the staging instance before restoring your production backup, your staging instance will use your production instance's external storage, which could result in loss of data. We strongly recommended that you use different external storage for your staging instance. For more information, see "[Using a staging environment](/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% data reusables.enterprise_installation.ssh-into-staging-instance %}
|
||||
1. To configure the staging instance to use an external storage provider for {% data variables.product.prodname_actions %}, enter one of the following commands.
|
||||
{% indented_data_reference reusables.actions.configure-storage-provider-platform-commands spaces=3 %}
|
||||
{% data reusables.actions.configure-storage-provider %}
|
||||
1. To prepare to enable {% data variables.product.prodname_actions %} on the staging instance, enter the following command.
|
||||
|
||||
```shell{:copy}
|
||||
ghe-config app.actions.enabled true
|
||||
```
|
||||
|
||||
### 4. Configure {% data variables.product.prodname_registry %}
|
||||
|
||||
Optionally, if you use {% data variables.product.prodname_registry %} on your production instance, configure the feature on the staging instance before restoring your production backup. If you don't use {% data variables.product.prodname_registry %}, skip to "[5. Restore your production backup](#5-restore-your-production-backup)."
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you don't configure {% data variables.product.prodname_actions %} on the staging instance before restoring your production backup, your staging instance will use your production instance's external storage, which could result in loss of data. We strongly recommended that you use different external storage for your staging instance.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
1. Review the backup you will restore to the staging instance.
|
||||
- If you took the backup with {% data variables.product.prodname_enterprise_backup_utilities %} 3.5 or later, the backup includes the configuration for {% data variables.product.prodname_registry %}. Continue to the next step.
|
||||
- If you took the backup with {% data variables.product.prodname_enterprise_backup_utilities %} 3.4 or earlier, configure {% data variables.product.prodname_registry %} on the staging instance. For more information, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
|
||||
{% data reusables.enterprise_installation.ssh-into-staging-instance %}
|
||||
1. Configure the external storage connection by entering the following commands, replacing the placeholder values with actual values for your connection.
|
||||
- Azure Blob Storage:
|
||||
|
||||
```shell{:copy}
|
||||
ghe-config secrets.packages.blob-storage-type "azure"
|
||||
ghe-config secrets.packages.azure-container-name "AZURE CONTAINER NAME"
|
||||
ghe-config secrets.packages.azure-connection-string "CONNECTION STRING"
|
||||
```
|
||||
- Amazon S3:
|
||||
|
||||
```shell{:copy}
|
||||
ghe-config secrets.packages.blob-storage-type "s3"
|
||||
ghe-config secrets.packages.service-url "S3 SERVICE URL"
|
||||
ghe-config secrets.packages.s3-bucket "S3 BUCKET NAME"
|
||||
ghe-config secrets.packages.aws-access-key "S3 ACCESS KEY ID"
|
||||
ghe-config secrets.packages.aws-secret-key "S3 ACCESS SECRET"
|
||||
```
|
||||
1. To prepare to enable {% data variables.product.prodname_registry %} on the staging instance, enter the following command.
|
||||
|
||||
```shell{:copy}
|
||||
ghe-config app.packages.enabled true
|
||||
```
|
||||
|
||||
### 5. Restore your production backup
|
||||
|
||||
Use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)."
|
||||
|
||||
If the staging instance is already configured and you're about to overwrite settings, certificate, and license data, add the `-c` option to the command. For more information about the option, see [Using the backup and restore commands](https://github.com/github/backup-utils/blob/master/docs/usage.md#restoring-settings-tls-certificate-and-license) in the {% data variables.product.prodname_enterprise_backup_utilities %} documentation.
|
||||
|
||||
### 6. Review the instance's configuration
|
||||
|
||||
To access the staging instance using the same hostname, update your local hosts file to resolve the staging instance's hostname by IP address by editing the `/etc/hosts` file in macOS or Linux, or the `C:\Windows\system32\drivers\etc` file in Windows.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Your staging instance must be accessible from the same hostname as your production instance. Changing the hostname for {% data variables.product.product_location %} is not supported. For more information, see "[Configuring a hostname](/admin/configuration/configuring-network-settings/configuring-a-hostname)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Then, review the staging instance's configuration in the {% data variables.enterprise.management_console %}. For more information, see "[Accessing the {% data variables.enterprise.management_console %}](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you configured {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} for the staging instance, to avoid overwriting production data, ensure that the external storage configuration in the {% data variables.enterprise.management_console %} does not match your production instance.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### 7. Apply the instance's configuration
|
||||
|
||||
To apply the configuration from the {% data variables.enterprise.management_console %}, click **Save settings**.
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"
|
||||
|
||||
@@ -150,7 +150,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>⌘</kbd>+<kbd>f</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>f</kbd> (Windows/Linux) | Focus filter field
|
||||
|<kbd>Command</kbd>+<kbd>f</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>f</kbd> (Windows/Linux) | Focus filter field
|
||||
|<kbd>←</kbd> | Move cell focus to the left
|
||||
|<kbd>→</kbd> | Move cell focus to the right
|
||||
|<kbd>↑</kbd> | Move cell focus up
|
||||
@@ -162,7 +162,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
|
||||
|-----------|------------
|
||||
|<kbd>Enter</kbd> | Toggle edit mode for the focused cell
|
||||
|<kbd>Escape</kbd> | Cancel editing for the focused cell
|
||||
|<kbd>⌘</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> (Windows/Linux) | Open row actions menu
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> (Windows/Linux) | Open row actions menu
|
||||
|<kbd>Shift</kbd>+<kbd>Space</kbd> | Select item
|
||||
|<kbd>Space</kbd> | Open selected item
|
||||
|<kbd>e</kbd> | Archive selected items
|
||||
|
||||
@@ -75,6 +75,10 @@ childGroups:
|
||||
octicon: ShieldLockIcon
|
||||
children:
|
||||
- code-security
|
||||
- code-security/supply-chain-security
|
||||
- code-security/dependabot
|
||||
- code-security/code-scanning
|
||||
- code-security/secret-scanning
|
||||
- name: Client apps
|
||||
octicon: DeviceMobileIcon
|
||||
children:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 管理组织的安全和分析设置
|
||||
intro: '您可以控制功能以保护组织在 {% data variables.product.prodname_dotcom %} 上项目的安全并分析其中的代码。'
|
||||
title: Managing security and analysis settings for your organization
|
||||
intro: 'You can control features that secure and analyze the code in your organization''s projects on {% data variables.product.prodname_dotcom %}.'
|
||||
permissions: Organization owners can manage security and analysis settings for repositories in the organization.
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization
|
||||
@@ -15,115 +15,156 @@ topics:
|
||||
- Organizations
|
||||
- Teams
|
||||
shortTitle: Manage security & analysis
|
||||
ms.openlocfilehash: 83104f606266279a239c5173e838c9241832fb84
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147063208'
|
||||
---
|
||||
## 关于安全性和分析设置的管理
|
||||
|
||||
{% data variables.product.prodname_dotcom %} 可帮助保护组织中的仓库。 您可以管理成员在组织中创建的所有现有或新仓库的安全性和分析功能。 {% ifversion ghec %}如果你拥有 {% data variables.product.prodname_GH_advanced_security %} 许可证，则还可以管理对这些功能的访问。 {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}使用 {% data variables.product.prodname_ghe_cloud %} 并拥有 {% data variables.product.prodname_GH_advanced_security %} 许可证的组织也可以管理对这些功能的访问。 有关详细信息，请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)。{% endif %}
|
||||
## About management of security and analysis settings
|
||||
|
||||
{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %}
|
||||
{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. {% ifversion ghec %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can also manage access to these features. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %}
|
||||
|
||||
## 显示安全和分析设置
|
||||
{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
|
||||
{% data reusables.security.security-and-analysis-features-enable-read-only %}
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security-and-analysis %}
|
||||
## Displaying the security and analysis settings
|
||||
|
||||
显示的页面允许您为组织中的仓库启用或禁用所有安全和分析功能。
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security-and-analysis %}
|
||||
|
||||
{% ifversion ghec %}如果你的组织属于具有 {% data variables.product.prodname_GH_advanced_security %} 许可证的企业，则该页面还会包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %}
|
||||
The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization.
|
||||
|
||||
{% ifversion ghes %}如果你的组织拥有 {% data variables.product.prodname_GH_advanced_security %} 许可证，则该页面还会包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %}
|
||||
{% ifversion ghec %}If your organization belongs to an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
|
||||
|
||||
{% ifversion ghae %}该页面还会包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %}
|
||||
{% ifversion ghes %}If you have a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
|
||||
|
||||
## 为所有现有存储库启用或禁用某项功能
|
||||
{% ifversion ghae %}The page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
|
||||
|
||||
您可以启用或禁用所有仓库的功能。 {% ifversion fpt or ghec %}您的更改对组织中仓库的影响取决于其可见性：
|
||||
## Enabling or disabling a feature for all existing repositories
|
||||
|
||||
- **依赖项关系图** - 所做的更改仅影响专用存储库，因为该功能对公共存储库始终启用。
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}** - 所做的更改会影响所有存储库。
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}** - 所做的更改会影响所有存储库。
|
||||
You can enable or disable features for all repositories.
|
||||
{% ifversion fpt or ghec %}The impact of your changes on repositories in your organization is determined by their visibility:
|
||||
|
||||
- **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories.
|
||||
- **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories.
|
||||
- **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories.
|
||||
{%- ifversion ghec %}
|
||||
- **{% data variables.product.prodname_GH_advanced_security %}** - 所做的更改仅影响专用存储库，因为 {% data variables.product.prodname_GH_advanced_security %} 和相关功能对公共存储库始终启用。
|
||||
- **{% data variables.product.prodname_secret_scanning_caps %}** - 所做的更改会影响同时启用了 {% data variables.product.prodname_GH_advanced_security %} 的存储库。 此选项控制是否启用 {% data variables.product.prodname_secret_scanning_GHAS %}。 {% data variables.product.prodname_secret_scanning_partner_caps %} 始终在所有公共存储库上运行。
|
||||
- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories.
|
||||
- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. This option controls whether or not {% data variables.product.prodname_secret_scanning_GHAS %} is enabled. {% data variables.product.prodname_secret_scanning_partner_caps %} always runs on all public repositories.
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.advanced-security.note-org-enable-uses-seats %}
|
||||
|
||||
1. 转到组织的安全和分析设置。 有关详细信息，请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
|
||||
2. 在“代码安全和分析”下，单击功能右侧的“全部禁用”或“全部启用” 。 {% ifversion ghes or ghec %}如果 {% data variables.product.prodname_GH_advanced_security %} 许可证中没有可用席位，则会禁用“{% data variables.product.prodname_GH_advanced_security %}”的控件。{% endif %} {% ifversion fpt %}  {% endif %} {% ifversion ghec %}  {% endif %} {% ifversion ghes > 3.2 %}  {% endif %} {% ifversion ghes = 3.2 %}  {% endif %}
|
||||
{% ifversion ghes or ghec or ghae %}
|
||||
{% note %}
|
||||
|
||||
**Note:** If you encounter an error that reads "GitHub Advanced Security cannot be enabled because of a policy setting for the organization," contact your enterprise admin and ask them to change the GitHub Advanced Security policy for your enterprise. For more information, see "[Enforcing policies for Advanced Security in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
|
||||
2. Under "Code security and analysis", to the right of the feature, click **Disable all** or **Enable all**. {% ifversion ghes or ghec %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.{% endif %}
|
||||
{% ifversion fpt %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghes > 3.2 %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghes = 3.2 %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}  {% endif %} {% ifversion fpt or ghec %}
|
||||
3. （可选）为组织中的新仓库默认启用该功能。
|
||||
{% ifversion fpt or ghec %}  {% endif %}
|
||||
{% ifversion ghae %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion fpt or ghec %}
|
||||
3. Optionally, enable the feature by default for new repositories in your organization.
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% endif %} {% ifversion fpt or ghec %}
|
||||
4. 单击“禁用功能”或“启用功能”，为组织中所有存储库禁用或启用该功能 。
|
||||
{% ifversion fpt or ghec %}  {% endif %}
|
||||
{% endif %}
|
||||
{% ifversion fpt or ghec %}
|
||||
4. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization.
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% endif %} {% ifversion ghae or ghes %}
|
||||
3. 单击“全部启用/禁用”或“为符合条件的存储库启用/禁用”以确认更改 。
|
||||
 {% endif %}
|
||||
{% endif %}
|
||||
{% ifversion ghae or ghes %}
|
||||
5. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.security.displayed-information %}
|
||||
|
||||
## 添加新仓库时自动启用或禁用功能
|
||||
## Enabling or disabling a feature automatically when new repositories are added
|
||||
|
||||
1. 转到组织的安全和分析设置。 有关详细信息，请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
|
||||
2. 在功能右边的“代码安全和分析”下，默认为组织中的新存储库{% ifversion fpt or ghec %}或所有新的专用存储库{% endif %}启用或禁用该功能。
|
||||
{% ifversion fpt or ghec %}  {% endif %} {% ifversion ghes > 3.2 %}  {% endif %} {% ifversion ghes = 3.2 %}  {% endif %} {% ifversion ghae %}  {% endif %}
|
||||
1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
|
||||
2. Under "Code security and analysis", to the right of the feature, enable or disable the feature by default for new repositories{% ifversion fpt or ghec %}, or all new private repositories,{% endif %} in your organization.
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghes > 3.2 %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghes = 3.2 %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghae %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
|
||||
## 允许 {% data variables.product.prodname_dependabot %} 访问私有依赖项
|
||||
## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies
|
||||
|
||||
{% data variables.product.prodname_dependabot %} 可以检查项目中过时的依赖项引用，并自动生成拉取请求来更新它们。 为此，{% data variables.product.prodname_dependabot %} 必须有权访问所有目标依赖项文件。 通常，如果一个或多个依赖项无法访问，版本更新将失败。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_dependabot %} 版本更新](/github/administering-a-repository/about-dependabot-version-updates)”。
|
||||
{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to all of the targeted dependency files. Typically, version updates will fail if one or more dependencies are inaccessible. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)."
|
||||
|
||||
默认情况下，{% data variables.product.prodname_dependabot %} 无法更新位于私有仓库或私有仓库注册表中的依赖项。 但是，如果依赖项位于与使用该依赖项之项目相同的组织内的私有 {% data variables.product.prodname_dotcom %} 仓库中，则可以通过授予对主机仓库的访问权限来允许 {% data variables.product.prodname_dependabot %} 成功更新版本。
|
||||
By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories or private package registries. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository.
|
||||
|
||||
如果您的代码依赖于私有注册表中的软件包，您可以在仓库级别进行配置，允许 {% data variables.product.prodname_dependabot %} 更新这些依赖项的版本。 可通过将身份验证详细信息添加到存储库的 dependabot.yml 文件来完成此操作。 有关详细信息，请参阅[dependabot.yml 文件的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)。
|
||||
If your code depends on packages in a private registry, you can allow {% data variables.product.prodname_dependabot %} to update the versions of these dependencies by configuring this at the repository level. You do this by adding authentication details to the _dependabot.yml_ file for the repository. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)."
|
||||
|
||||
要允许 {% data variables.product.prodname_dependabot %} 访问私有 {% data variables.product.prodname_dotcom %} 仓库：
|
||||
To allow {% data variables.product.prodname_dependabot %} to access a private {% data variables.product.prodname_dotcom %} repository:
|
||||
|
||||
1. 转到组织的安全和分析设置。 有关详细信息，请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
|
||||
1. 在“{% data variables.product.prodname_dependabot %} 专用存储库访问权限”下，单击“添加专用存储库”或“添加内部和专用存储库” 。
|
||||
|
||||
1. 开始键入要允许的存储库的名称。
|
||||
|
||||
1. 单击要允许的存储库。
|
||||
1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
|
||||
1. Under "{% data variables.product.prodname_dependabot %} private repository access", click **Add private repositories** or **Add internal and private repositories**.
|
||||
|
||||
1. Start typing the name of the repository you want to allow.
|
||||
|
||||
1. Click the repository you want to allow.
|
||||
|
||||
1. （可选）要从列表中删除仓库，在仓库右侧单击 {% octicon "x" aria-label="The X icon" %}。
|
||||
 {% endif %}
|
||||
1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghec %}
|
||||
|
||||
## 从组织中的个别仓库中移除对 {% data variables.product.prodname_GH_advanced_security %} 的访问权限
|
||||
## Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an organization
|
||||
|
||||
可以通过存储库的“设置”选项卡管理对存储库的 {% data variables.product.prodname_GH_advanced_security %} 功能的访问。有关详细信息，请参阅“[管理存储库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 但您也可以从“Settings（设置）”选项卡对仓库禁用 {% data variables.product.prodname_GH_advanced_security %} 功能。
|
||||
You can manage access to {% data variables.product.prodname_GH_advanced_security %} features for a repository from its "Settings" tab. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." However, you can also disable {% data variables.product.prodname_GH_advanced_security %} features for a repository from the "Settings" tab for the organization.
|
||||
|
||||
1. 转到组织的安全和分析设置。 有关详细信息，请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
|
||||
1. 要查看您组织中启用 {% data variables.product.prodname_GH_advanced_security %} 的所有仓库的列表，请滚动到“{% data variables.product.prodname_GH_advanced_security %} 仓库”部分。
|
||||
 此表列出了每个存储库的唯一提交者数量。 这是您可以通过移除 {% data variables.product.prodname_GH_advanced_security %} 访问权限释放的席位数。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 计费](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)。”
|
||||
1. 要从仓库删除对 {% data variables.product.prodname_GH_advanced_security %} 的访问，并释放任何提交者使用的对仓库唯一的席位，请单击相邻的 {% octicon "x" aria-label="X symbol" %}。
|
||||
1. 在确认对话框中，单击“删除存储库”以删除对 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限。
|
||||
1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
|
||||
1. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section.
|
||||
|
||||
The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."
|
||||
1. To remove access to {% data variables.product.prodname_GH_advanced_security %} from a repository and free up seats used by any committers that are unique to the repository, click the adjacent {% octicon "x" aria-label="X symbol" %}.
|
||||
1. In the confirmation dialog, click **Remove repository** to remove access to the features of {% data variables.product.prodname_GH_advanced_security %}.
|
||||
|
||||
{% note %}
|
||||
|
||||
注意：如果删除对存储库中 {% data variables.product.prodname_GH_advanced_security %} 的访问权限，则应与受影响的开发团队沟通，以便他们了解此更改是有意的。 这确保他们不会浪费时间调试运行失败的代码扫描。
|
||||
**Note:** If you remove access to {% data variables.product.prodname_GH_advanced_security %} for a repository, you should communicate with the affected development team so that they know that the change was intended. This ensures that they don't waste time debugging failed runs of code scanning.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- [保护存储库](/code-security/getting-started/securing-your-repository){% ifversion not fpt %}
|
||||
- [关于机密扫描](/github/administering-a-repository/about-secret-scanning){% endif %}{% ifversion not ghae %}
|
||||
- [关于依赖项关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph){% endif %}
|
||||
- [关于供应链安全性](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)
|
||||
- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %}
|
||||
- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
|
||||
- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}
|
||||
- "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)"
|
||||
|
||||
@@ -30,7 +30,7 @@ Prerequisites for repository transfers:
|
||||
- When you transfer a repository that you own to another personal account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %}
|
||||
- To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization.
|
||||
- The target account must not have a repository with the same name, or a fork in the same network.
|
||||
- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghes < 3.7 %}
|
||||
- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghes < 3.7 or ghae %}
|
||||
- Internal repositories can't be transferred.{% endif %}
|
||||
- Private forks can't be transferred.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user