зеркало из https://github.com/github/docs.git
New translation batch for cn (#28374)
* Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=cn * run script/i18n/reset-known-broken-translation-files.js * Check in cn CSV report
This commit is contained in:
docubot
GitHub
Родитель
5762a65351
Коммит
7175dd7378
|
|
@ -1,9 +1,9 @@
|
|||
file,reason
|
||||
translations/zh-CN/content/account-and-profile/index.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags
|
||||
|
|
@ -73,6 +73,7 @@ translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-
|
|||
translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/index.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/index.md,rendering error
|
||||
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/username-considerations-for-external-authentication.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md,broken liquid tags
|
||||
|
|
@ -88,7 +89,7 @@ translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzin
|
|||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,Listed in localization-support#489
|
||||
translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,rendering error
|
||||
translations/zh-CN/content/admin/overview/creating-an-enterprise-account.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags
|
||||
|
|
|
|||
|
|
|
@ -17,7 +17,7 @@ featuredLinks:
|
|||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
|
||||
- /account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications
|
||||
guideCards:
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address
|
||||
- '{% ifversion ghes or ghae %}/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories{% endif %}'
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ topics:
|
|||
- 你拥有或参与的仓库和 gists。 {% ifversion fpt or ghes or ghec %}您可以通过将仓库和 Gist 固定到个人资料中来展示您的最佳作品。 更多信息请参阅“[将项目嵌入到个人资料](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)”。{% endif %}
|
||||
- 您已加星标{% ifversion fpt or ghec %} 并组织到列表中的存储库。{% endif %} 更多信息请参阅“[保存有星标的存储库](/articles/saving-repositories-with-stars/)”。
|
||||
- 您在经常参与的组织、仓库和团队中的活动概述。 更多信息请参阅“[在您的个人资料中显示活动概述](/articles/showing-an-overview-of-your-activity-on-your-profile)”。{% ifversion fpt or ghec %}
|
||||
- 徽章，显示您是否使用 {% data variables.product.prodname_pro %} 或参与计划，例如 {% data variables.product.prodname_arctic_vault %}、{% data variables.product.prodname_sponsors %} 或 {% data variables.product.company_short %} 开发者计划。 更多信息请参阅“[个性化您的个人资料](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)”。{% endif %}
|
||||
- Badges and Achievements that highlight your activity and show if you use {% data variables.product.prodname_pro %} or participate in programs like the {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %}, or the {% data variables.product.company_short %} Developer Program. 更多信息请参阅“[个性化您的个人资料](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)”。{% endif %}
|
||||
|
||||
您还可以在个人资料上设置状态，以提供有关您的可用性的信息。 更多信息请参阅“[设置状态](/articles/personalizing-your-profile/#setting-a-status)”。
|
||||
|
||||
|
|
|
|||
|
|
@ -120,10 +120,7 @@ shortTitle: 个性化
|
|||
当您参与某些计划时， {% data variables.product.prodname_dotcom %} 会自动在您的个人资料中显示徽章。
|
||||
|
||||
| 徽章 | 计划 | 描述 |
|
||||
| ------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
|  | **Mars 2020 Helicopter 贡献者** | 如果您在提交历史记录中撰写了对 Mars 2020 Helicopter 任务中使用的开放源码库相关标记的任何提交， 您将在个人资料上获得 Mars 2020 Helicopter 贡献者徽章。 悬停在徽章上会显示您参与的任务中使用的几个仓库。 要查看符合您徽章资格的完整仓库列表，请参阅“[Mars 2020 Helicopter 贡献者徽章的合格仓库列表](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)”。 |
|
||||
|  | **{% data variables.product.prodname_arctic_vault %} 贡献者** | 如果您在存档于 2020 Arctic Vault 计划的仓库默认分支上编写了任何提交，您的个人资料上会获得一个 {% data variables.product.prodname_arctic_vault %} 贡献者徽章。 悬停在徽章上显示您参与的属于计划一部分的几个仓库。 有关该计划的更多信息，请参阅 [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com)。 |
|
||||
|  | **{% data variables.product.prodname_dotcom %} 赞助者** | 如果您通过 {% data variables.product.prodname_sponsors %} 赞助了开源贡献者，您的个人资料中将获得一个 {% data variables.product.prodname_dotcom %} 赞助者徽章。 单击徽章将带您到个人资料的 **Sponsoring（赞助）**选项卡。 更多信息请参阅“[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)”。 |
|
||||
| --------------------------------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| {% 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/)。 |
|
||||
|
|
@ -131,19 +128,27 @@ shortTitle: 个性化
|
|||
| {% 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 的更多信息，请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。 |
|
||||
|
||||
## 在个人资料中禁用徽章
|
||||
{% endif %}
|
||||
|
||||
您可以对您参与的 {% data variables.product.prodname_dotcom %} 计划禁用某些徽章，包括 PRO、{% data variables.product.prodname_arctic_vault %} 和 Mars 2020 Helicopter 贡献者徽章。
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
2. 在“Profile settings（个人资料设置）”下，取消选择您想要禁用的徽章。 
|
||||
{% data reusables.user-settings.update-preferences %}
|
||||
## Earning Achievements
|
||||
|
||||
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.
|
||||
|
||||
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 %}
|
||||
|
||||
**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. 撰写的提交必须有验证过的电子邮件地址，该电子邮件地址在 {% data variables.product.prodname_dotcom %} 确定符合条件的贡献时与您帐户关联，表示该贡献归属于您。 您可以是提交的原始作者或 [共同作者](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)。 将来对经过验证的电子邮件的更改不会对徽章产生影响。 我们根据从美国航天局喷气推进实验室获得的资料编制了清单。
|
||||
|
||||
| {% data variables.product.prodname_dotcom %} 仓库 | 版本 | 标记 |
|
||||
| ----------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------- |
|
||||
|
|
|
|||
|
|
@ -14,6 +14,6 @@ topics:
|
|||
- Profiles
|
||||
children:
|
||||
- /customizing-your-profile
|
||||
- /managing-contribution-graphs-on-your-profile
|
||||
- /managing-contribution-settings-on-your-profile
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +1,10 @@
|
|||
---
|
||||
title: 管理个人资料中的贡献图
|
||||
title: Managing contribution settings on your profile
|
||||
intro: 您的贡献（包括提交、提议的拉取请求和打开的议题）将显示在个人资料中，便于人们轻松看到您所做的工作。
|
||||
redirect_from:
|
||||
- /articles/managing-contribution-graphs-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
|
@ -14,10 +15,10 @@ topics:
|
|||
children:
|
||||
- /viewing-contributions-on-your-profile
|
||||
- /showing-an-overview-of-your-activity-on-your-profile
|
||||
- /publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
- /showing-your-private-contributions-and-achievements-on-your-profile
|
||||
- /sending-enterprise-contributions-to-your-githubcom-profile
|
||||
- /why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /troubleshooting-commits-on-your-timeline
|
||||
shortTitle: 管理贡献图
|
||||
shortTitle: Manage contribution settings
|
||||
---
|
||||
|
||||
|
|
@ -7,6 +7,7 @@ redirect_from:
|
|||
- /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
|
@ -5,6 +5,7 @@ redirect_from:
|
|||
- /articles/showing-an-overview-of-your-activity-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
|
@ -1,10 +1,11 @@
|
|||
---
|
||||
title: 在个人资料中公开或隐藏您的私人贡献
|
||||
title: Showing your private contributions and achievements on your profile
|
||||
intro: '您的 {% data variables.product.product_name %} 个人资料显示过去一年中您的仓库贡献图。 除了公共存储库的活动外，您还可以选择显示 {% ifversion fpt or ghes or ghec %}私人和内部{% else %}私人{% endif %} 仓库中的匿名活动{% ifversion fpt or ghes or ghec %}{% endif %}。'
|
||||
redirect_from:
|
||||
- /articles/publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
|
@ -12,7 +13,7 @@ versions:
|
|||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: 私有贡献
|
||||
shortTitle: Private contributions and achievements
|
||||
---
|
||||
|
||||
如果公开您的私有贡献，对您处理的私有仓库没有访问权限的人员将无法查看您的私有贡献详情， 而只能看到您在指定日期的贡献数。 您的公共贡献会包含详细信息。 更多信息请参阅“[在个人资料页面中查看贡献](/articles/viewing-contributions-on-your-profile-page)”。
|
||||
|
|
@ -30,6 +31,13 @@ shortTitle: 私有贡献
|
|||
- 要公开您的私有贡献，在贡献图上方，使用 **Contribution settings（贡献设置）**下拉菜单，然后选择 **Private contributions（私有贡献）**。 访问者将会看到您的私有贡献数，但没有更多详细信息。 
|
||||
- 要隐藏您的私有贡献，在贡献图上方，使用 **Contribution settings（贡献设置）**下拉菜单，然后取消选择 **Private contributions（私有贡献）**。访问者只会看到您的公共贡献。 
|
||||
|
||||
## Changing the visibility of Achievements
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
1. Show or hide Achievements on your profile:
|
||||
- To show Achievements on your profile, navigate to **Profile settings**, and select the checkbox next to **Show Achievements on my profile.** 
|
||||
- To hide Achievements from your profile, navigate to **Profile settings**, and unselect the checkbox next to **Show Achievements on my profile.** 
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[在个人资料页面中查看贡献](/articles/viewing-contributions-on-your-profile-page)"
|
||||
|
|
@ -5,6 +5,7 @@ redirect_from:
|
|||
- /articles/troubleshooting-commits-on-your-timeline
|
||||
- /github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Viewing contributions on your profile
|
||||
intro: 'Your {% data variables.product.product_name %} profile shows off {% ifversion fpt or ghes or ghec %}your pinned repositories as well as{% endif %} a graph of your repository contributions over the past year.'
|
||||
intro: 'Your {% data variables.product.product_name %} profile shows off {% ifversion fpt or ghes or ghec %}your pinned repositories, Achievements, and{% endif %} a graph of your repository contributions over the past year.'
|
||||
redirect_from:
|
||||
- /articles/viewing-contributions
|
||||
- /articles/viewing-contributions-on-your-profile-page
|
||||
|
|
@ -16,7 +16,7 @@ topics:
|
|||
- Profiles
|
||||
shortTitle: View contributions
|
||||
---
|
||||
{% ifversion fpt or ghes or ghec %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% ifversion fpt or ghes or ghec %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
|
||||
{% ifversion fpt or ghes or ghec %}Your contribution graph and Achievements show activity from public repositories. {% endif %}You can choose to show activity from {% ifversion fpt or ghes or ghec %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
@ -5,6 +5,7 @@ redirect_from:
|
|||
- /articles/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
|
@ -22,7 +22,7 @@ shortTitle: 构建和测试 Java & Gradle
|
|||
|
||||
## 简介
|
||||
|
||||
本指南介绍如何使用 Gradle 构建系统为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 You can extend your CI workflow to {% ifversion actions-caching %}cache files and{% endif %} upload artifacts from a workflow run.
|
||||
本指南介绍如何使用 Gradle 构建系统为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以{% ifversion actions-caching %}缓存文件并且{% endif %}从工作流程运行上传构件。
|
||||
|
||||
{% ifversion ghae %}
|
||||
{% data reusables.actions.self-hosted-runners-software %}
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ shortTitle: 使用 Maven 构建和测试 Java
|
|||
|
||||
## 简介
|
||||
|
||||
本指南介绍如何使用 Maven 软件项目管理工具为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 You can extend your CI workflow to {% ifversion actions-caching %}cache files and{% endif %} upload artifacts from a workflow run.
|
||||
本指南介绍如何使用 Maven 软件项目管理工具为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以{% ifversion actions-caching %}缓存文件并且{% endif %}从工作流程运行上传构件。
|
||||
|
||||
{% ifversion ghae %}
|
||||
{% data reusables.actions.self-hosted-runners-software %}
|
||||
|
|
|
|||
|
|
@ -134,7 +134,7 @@ jobs:
|
|||
|
||||
{% data variables.product.prodname_dotcom %} 托管的运行器安装了 npm 和 Yarn 依赖项管理器。 在构建和测试代码之前，可以使用 npm 和 Yarn 在工作流程中安装依赖项。 Windows 和 Linux {% data variables.product.prodname_dotcom %} 托管的运行器也安装了 Grunt、Gulp 和 Bower。
|
||||
|
||||
{% ifversion actions-caching %}You can also cache dependencies to speed up your workflow. 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。{% endif %}
|
||||
{% ifversion actions-caching %}您也可以缓存依赖项来加快工作流程。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。{% endif %}
|
||||
|
||||
### 使用 npm 的示例
|
||||
|
||||
|
|
|
|||
|
|
@ -104,7 +104,7 @@ jobs:
|
|||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion actions-caching %}You can also cache dependencies to speed up your workflow. 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。{% endif %}
|
||||
{% ifversion actions-caching %}您也可以缓存依赖项来加快工作流程。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。{% endif %}
|
||||
|
||||
例如，以下作业将安装 `SqlServer` 和 `PSScriptAnalyzer` 模块：
|
||||
|
||||
|
|
|
|||
|
|
@ -195,7 +195,7 @@ jobs:
|
|||
|
||||
{% data variables.product.prodname_dotcom %} 托管的运行器安装了 pip 软件包管理器。 在构建和测试代码之前，您可以使用 pip 从 PyPI 软件包注册表安装依赖项。 例如，下面的 YAML 安装或升级 `pip` 软件包安装程序以及 `setuptools` 和 `wheel` 软件包。
|
||||
|
||||
{% ifversion actions-caching %}You can also cache dependencies to speed up your workflow. 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。{% endif %}
|
||||
{% ifversion actions-caching %}您也可以缓存依赖项来加快工作流程。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。{% endif %}
|
||||
|
||||
```yaml{:copy}
|
||||
steps:
|
||||
|
|
|
|||
|
|
@ -137,6 +137,14 @@ gh run rerun --job <em>job-id</em> --debug
|
|||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion partial-reruns-with-reusable %}
|
||||
|
||||
## Re-running workflows and jobs with reusable workflows
|
||||
|
||||
{% data reusables.actions.partial-reruns-with-reusable %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.4 or ghae-issue-4721 or ghec %}
|
||||
## 查看以前的工作流程运行
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ shortTitle: 跳过工作流程运行
|
|||
* `[skip actions]`
|
||||
* `[actions skip]`
|
||||
|
||||
Alternatively, you can end the commit message with two empty lines followed by either:
|
||||
或者，您可以用两个空行后跟以下任一行结束提交消息：
|
||||
- `skip-checks:true`
|
||||
- `skip-checks: true`
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: 连接到专用网络
|
||||
intro: 'You can connect {% data variables.product.prodname_dotcom %}-hosted runners to resources on a private network, including package registries, secret managers, and other on-premises services.'
|
||||
intro: '可以将 {% data variables.product.prodname_dotcom %} 托管的运行器连接到专用网络上的资源，包括包注册表、机密管理器和其他本地服务。'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
|
@ -14,57 +14,57 @@ topics:
|
|||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## About {% data variables.product.prodname_dotcom %}-hosted runners networking
|
||||
## 关于 {% data variables.product.prodname_dotcom %} 托管的运行器联网
|
||||
|
||||
By default, {% data variables.product.prodname_dotcom %}-hosted runners have access to the public internet. However, you may also want these runners to access resources on your private network, such as a package registry, a secret manager, or other on-premise services.
|
||||
默认情况下，{% data variables.product.prodname_dotcom %} 托管的运行器可以访问公共互联网。 但是，您可能还希望这些运行器访问专用网络上的资源，例如程序包注册表、机密管理器或其他本地服务。
|
||||
|
||||
{% data variables.product.prodname_dotcom %}-hosted runners are shared across all {% data variables.product.prodname_dotcom %} customers, so you will need a way of connecting your private network to just your runners while they are running your workflows. There are a few different approaches you could take to configure this access, each with different advantages and disadvantages.
|
||||
{% data variables.product.prodname_dotcom %} 托管的运行器在所有 {% data variables.product.prodname_dotcom %} 客户之间共享，因此您需要一种方法，在运行器运行工作流程时，将您的专用网络仅连接到他们的运行器。 您可以采取几种不同的方法来配置此访问，每种方法都有不同的优点和缺点。
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
### Using an API Gateway with OIDC
|
||||
### 将 API 网关与 OIDC 配合使用
|
||||
|
||||
With {% data variables.product.prodname_actions %}, you can use OpenID Connect (OIDC) tokens to authenticate your workflow outside of {% data variables.product.prodname_actions %}. For example, you could run an API Gateway on the edge of your private network that authenticates incoming requests with the OIDC token and then makes API requests on behalf of your workflow in your private network.
|
||||
借助 {% data variables.product.prodname_actions %}，您可以使用 OpenID Connect (OIDC) 令牌在 {% data variables.product.prodname_actions %} 之外验证工作流程。 例如，您可以在专用网络的边缘运行 API 网关，该网关使用 OIDC 令牌对传入请求进行身份验证，然后代表专用网络中的工作流程发出 API 请求。
|
||||
|
||||
The following diagram gives an overview of this solution's architecture:
|
||||
下图概述了此解决方案的架构：
|
||||
|
||||
|
||||
|
||||
|
||||
It's important that you authenticate not just that the OIDC token came from {% data variables.product.prodname_actions %}, but that it came specifically from your expected workflows, so that other {% data variables.product.prodname_actions %} users aren't able to access services in your private network. You can use OIDC claims to create these conditions. For more information, see "[Defining trust conditions on cloud roles using OIDC claims](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#defining-trust-conditions-on-cloud-roles-using-oidc-claims)."
|
||||
重要的是，您不仅要验证 OIDC 令牌来自 {% data variables.product.prodname_actions %}，还要特别验证它来自预期的工作流程，以便其他 {% data variables.product.prodname_actions %} 用户无法访问您的专用网络中的服务。 您可以使用 OIDC 声明来创建这些条件。 更多信息请参阅“[使用 OIDC 声明定义云角色上的信任条件](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#defining-trust-conditions-on-cloud-roles-using-oidc-claims)”。
|
||||
|
||||
The main disadvantage of this approach is you have to implement the API gateway to make requests on your behalf, as well as run it on the edge of your network.
|
||||
此方法的主要缺点是您必须实现 API 网关以代表您发出请求，并在网络边界运行它。
|
||||
|
||||
But there are various advantages too:
|
||||
- You don't need to configure any firewalls, or modify the routing of your private network.
|
||||
- The API gateway is stateless, and so it scales horizontally to handle high availability and high throughput.
|
||||
但也有各种优点：
|
||||
- 您无需配置任何防火墙，也无需修改专用网络的路由。
|
||||
- API 网关是无状态的，因此可以水平扩展以处理高可用性和高吞吐量。
|
||||
|
||||
For more information, see [a reference implementation of an API Gateway](https://github.com/github/actions-oidc-gateway-example) (note that this requires customization for your use case and is not ready-to-run as-is), and "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)".
|
||||
更多信息请参阅 [API Gateway 的参考实现](https://github.com/github/actions-oidc-gateway-example)（请注意，这需要针对您的使用情况进行自定义，并且不能按原样运行）和[关于使用 OpenID Connect 进行安全强化](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)”。
|
||||
{% endif %}
|
||||
|
||||
### Using WireGuard to create a network overlay
|
||||
### 使用 WireGuard 创建网络覆盖
|
||||
|
||||
If you don't want to maintain separate infrastructure for an API Gateway, you can create an overlay network between your runner and a service in your private network, by running WireGuard in both places.
|
||||
如果您不想为 API Gateway 维护单独的基础设施，则可以通过在两个地方运行 WireGuard，在运行器和专用网络中的服务之间创建一个覆盖网络。
|
||||
|
||||
There are various disadvantages to this approach:
|
||||
这种方法有几个缺点：
|
||||
|
||||
- To reach WireGuard running on your private service, you will need a well-known IP address and port that your workflow can reference: this can either be a public IP address and port, a port mapping on a network gateway, or a service that dynamically updates DNS.
|
||||
- WireGuard doesn't handle NAT traversal out of the box, so you'll need to identify a way to provide this service.
|
||||
- This connection is one-to-one, so if you need high availability or high throughput you'll need to build that on top of WireGuard.
|
||||
- You'll need to generate and securely store keys for both the runner and your private service. WireGuard uses UDP, so your network must support UDP traffic.
|
||||
- 要访问在专用服务上运行的 WireGuard，需要工作流程可以引用的已知 IP 地址和端口：这可以是公共 IP 地址和端口、网络网关上的端口映射或动态更新 DNS 的服务。
|
||||
- WireGuard 不会开箱即用地处理 NAT 遍历，因此您需要确定一种提供此服务的方法。
|
||||
- 这种连接是一对一的，因此，如果需要高可用性或高吞吐量，则需要在WireGuard 之上构建它。
|
||||
- 您需要为运行器和私有服务生成并安全地存储密钥。 WireGuard 使用 UDP，因此您的网络必须支持 UDP 流量。
|
||||
|
||||
There are some advantages too, as you can run WireGuard on an existing server so you don't have to maintain separate infrastructure, and it's well supported on {% data variables.product.prodname_dotcom %}-hosted runners.
|
||||
还有一些优点，因为您可以在现有的服务器上运行 WireGuard，所以你不必维护单独的基础设施，而且它在 {% data variables.product.prodname_dotcom %} 托管的运行器上得到了很好的支持。
|
||||
|
||||
### Example: Configuring WireGuard
|
||||
### 示例：配置 WireGuard
|
||||
|
||||
This example workflow configures WireGuard to connect to a private service.
|
||||
此示例工作流程将 WireGuard 配置为连接到专用服务。
|
||||
|
||||
For this example, the WireGuard instance running in the private network has this configuration:
|
||||
- Overlay network IP address of `192.168.1.1`
|
||||
- Public IP address and port of `1.2.3.4:56789`
|
||||
- Public key `examplepubkey1234...`
|
||||
对于此示例，在专用网络中运行的 WireGuard 实例具有以下配置：
|
||||
- `192.168.1.1` 的覆盖网络 IP 地址
|
||||
- `1.2.3.4:56789` 的公共 IP 地址和端口
|
||||
- 公钥 `examplepubkey1234...`
|
||||
|
||||
The WireGuard instance in the {% data variables.product.prodname_actions %} runner has this configuration:
|
||||
- Overlay network IP address of `192.168.1.2`
|
||||
- Private key stores as an {% data variables.product.prodname_actions %} secret under `WIREGUARD_PRIVATE_KEY`
|
||||
{% data variables.product.prodname_actions %} 运行器中的 WireGuard 实例具有以下配置：
|
||||
- `192.168.1.2` 的覆盖网络 IP 地址
|
||||
- 私钥作为 {% data variables.product.prodname_actions %} 机密存储在 `WIREGUARD_PRIVATE_KEY`下
|
||||
|
||||
```yaml
|
||||
name: WireGuard example
|
||||
|
|
@ -91,14 +91,14 @@ jobs:
|
|||
- run: curl -vvv http://192.168.1.1
|
||||
```
|
||||
|
||||
For more information, see [WireGuard's Quick Start](https://www.wireguard.com/quickstart/), as well as "[Encrypted Secrets](/actions/security-guides/encrypted-secrets)" for how to securely store keys.
|
||||
有关更多信息，请参阅 [WireGuard 快速入门](https://www.wireguard.com/quickstart/)，以及“[加密机密](/actions/security-guides/encrypted-secrets)”了解如何安全存储密钥。
|
||||
|
||||
### Using Tailscale to create a network overlay
|
||||
### 使用 Tailscale 创建网络叠加
|
||||
|
||||
Tailscale is a commercial product built on top of WireGuard. This option is very similar to WireGuard, except Tailscale is more of a complete product experience instead of an open source component.
|
||||
Tailscale 是建立在 WireGuard 之上的商业产品。 此选项与 WireGuard 非常相似，除了 Tailscale 更像是完整的产品体验，而不是开源组件。
|
||||
|
||||
It's disadvantages are similar to WireGuard: The connection is one-to-one, so you might need to do additional work for high availability or high throughput. You still need to generate and securely store keys. The protocol is still UDP, so your network must support UDP traffic.
|
||||
它的缺点与 WireGuard 类似：连接是一对一的，因此您可能需要执行额外的工作以实现高可用性或高吞吐量。 您仍然需要生成并安全地存储密钥。 该协议仍然是 UDP，因此您的网络必须支持 UDP 流量。
|
||||
|
||||
However, there are some advantages over WireGuard: NAT traversal is built-in, so you don't need to expose a port to the public internet. It is by far the quickest of these options to get up and running, since Tailscale provides an {% data variables.product.prodname_actions %} workflow with a single step to connect to the overlay network.
|
||||
但与 WireGuard 相比有一些优势：NAT 遍历是内置的，因此您无需向公共互联网公开端口。 到目前为止，它是这些选项中启动和运行最快的选项，因为 Tailscale 提供 {% data variables.product.prodname_actions %} 工作流程，只需一步即可连接到覆盖网络。
|
||||
|
||||
For more information, see the [Tailscale GitHub Action](https://github.com/tailscale/github-action), as well as "[Encrypted Secrets](/actions/security-guides/encrypted-secrets)" for how to securely store keys.
|
||||
更多信息请参阅 [Tailscale GitHub Action](https://github.com/tailscale/github-action)，以及参阅“[加密机密](/actions/security-guides/encrypted-secrets)”，了解如何安全存储密钥。
|
||||
|
|
|
|||
|
|
@ -257,7 +257,7 @@ restore-keys: |
|
|||
|
||||
## 使用限制和收回政策
|
||||
|
||||
{% data variables.product.prodname_dotcom %} 将删除 7 天内未被访问的任何缓存条目。 There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited{% ifversion actions-cache-policy-apis %}. 默认情况下，每个存储库的限制为 10 GB，但此限制可能会有所不同，具体取决于企业所有者或存储库管理员设置的策略。{% else %} 10 GB。{% endif %}
|
||||
{% data variables.product.prodname_dotcom %} 将删除 7 天内未被访问的任何缓存条目。 可以存储的缓存数没有限制，但存储库中所有缓存的总大小限制为{% ifversion actions-cache-policy-apis %} 默认情况下，每个存储库的限制为 10 GB，但此限制可能会有所不同，具体取决于企业所有者或存储库管理员设置的策略。{% else %} 10 GB。{% endif %}
|
||||
|
||||
{% data reusables.actions.cache-eviction-process %}
|
||||
|
||||
|
|
|
|||
|
|
@ -310,6 +310,14 @@ For information about using the REST API to query the audit log for an organizat
|
|||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion partial-reruns-with-reusable %}
|
||||
|
||||
## Re-running workflows and jobs with reusable workflows
|
||||
|
||||
{% data reusables.actions.partial-reruns-with-reusable %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Next steps
|
||||
|
||||
To continue learning about {% data variables.product.prodname_actions %}, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)."
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: 关于企业的身份验证
|
||||
shortTitle: 关于身份验证
|
||||
intro: '您必须 {% ifversion ghae %}配置 SAML 单点登录 (SSO)，以便用户可以{% else %}可以选择人员如何{% endif %} 进行身份验证，以便访问{% ifversion ghec %} {% data variables.product.product_name %} 上的企业资源{% elsif ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}上的企业{% endif %}。'
|
||||
title: About authentication for your enterprise
|
||||
shortTitle: About authentication
|
||||
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.product.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}.
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
|
|
@ -15,37 +15,37 @@ topics:
|
|||
- SSO
|
||||
---
|
||||
|
||||
## 关于企业的身份验证
|
||||
## 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.
|
||||
|
||||
You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. 如果您允许成员管理自己的帐户，则还可以配置 SAML 身份验证，以提高安全性，并集中团队使用的 Web 应用程序的身份和访问权限。
|
||||
You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. If you allow members to manage their own accounts, you can also configure SAML authentication to both increase security and centralize identity and access for the web applications that your team uses.
|
||||
|
||||
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.product.product_location %} 进行身份验证](#authentication-through-githubcom)
|
||||
- [通过具有附加 SAML 访问限制的 {% data variables.product.product_location %} 进行身份验证](#authentication-through-githubcom-with-additional-saml-access-restriction)
|
||||
- [Authentication through {% data variables.product.product_location %}](#authentication-through-githubcom)
|
||||
- [Authentication through {% data variables.product.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.product.product_location %} 进行身份验证
|
||||
### Authentication through {% data variables.product.product_location %}
|
||||
|
||||
默认情况下，每个成员都必须在 {% data variables.product.product_location %} 上创建个人帐户。 您授予对企业的访问权限，该成员可以在登录 {% data variables.product.product_location %} 上的帐户后访问您企业的资源。 该成员管理该帐户，并且可以为 {% data variables.product.product_location %} 上的其他企业、组织和存储库做出贡献。
|
||||
By default, each member must create a personal account on {% data variables.product.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.product.product_location %}. The member manages the account, and can contribute to other enterprises, organizations, and repositories on {% data variables.product.product_location %}.
|
||||
|
||||
### 通过具有附加 SAML 访问限制的 {% data variables.product.product_location %} 进行身份验证
|
||||
### Authentication through {% data variables.product.product_location %} with additional SAML access restriction
|
||||
|
||||
如果配置了其他 SAML 访问限制，则每个成员都必须在 {% data variables.product.product_location %} 上创建和管理个人帐户。 您授予对企业的访问权限，在 {% data variables.product.product_location %} 登录账户并使用 SAML 身份提供程序 (IdP) 成功进行身份验证后，成员可以访问您企业的资源。 成员可以使用其个人帐户向在 {% data variables.product.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.product.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.product.product_location %} and successfully authenticating with your SAML identity provider (IdP). The member can contribute to other enterprises, organizations, and repositories on {% data variables.product.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)."
|
||||
|
||||
### Authentication with {% data variables.product.prodname_emus %} and federation
|
||||
|
||||
如果您需要增强控制您在 {% data variables.product.product_location %} 上的企业成员的帐户，则可以使用 {% data variables.product.prodname_emus %}。 借助 {% data variables.product.prodname_emus %}，您可以使用 IdP 在 {% data variables.product.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.product.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.product.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
|
||||
|
||||
|
|
@ -100,39 +100,39 @@ Although {% data variables.product.prodname_emus %} is free, the migration proce
|
|||
|
||||
{% 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.product.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.product.product_location %}. For more information, see the following.
|
||||
|
||||
- “[将 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)."
|
||||
|
||||
{% 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)”
|
||||
- "[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 %}
|
||||
- “[是否可以为组织中的人员创建帐户？](/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization)”
|
||||
- "[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 %}
|
||||
|
|
@ -28,11 +28,11 @@ redirect_from:
|
|||
|
||||
{% ifversion ghec %}
|
||||
|
||||
If your enterprise members manage their own user accounts on {% data variables.product.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %}
|
||||
如果您的企业成员在 {% data variables.product.product_location %} 上管理自己的用户帐户，则可以将 SAML 身份验证配置为企业或组织的额外访问限制。 {% data reusables.saml.dotcom-saml-explanation %}
|
||||
|
||||
{% data reusables.saml.about-saml-enterprise-accounts %} 更多信息请参阅“[配置企业的 SAML 单点登录](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。
|
||||
|
||||
Alternatively, you can provision and manage the accounts of your enterprise members with {% data variables.product.prodname_emus %}. To help you determine whether SAML SSO or {% data variables.product.prodname_emus %} is better for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)."
|
||||
或者，您可以使用 {% data variables.product.prodname_emus %} 来配置和管理企业成员的帐户。 为了帮助您确定 SAML SSO 或 {% data variables.product.prodname_emus %} 是否更适合您的企业，请参阅“[关于企业的身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)”。
|
||||
|
||||
{% data reusables.enterprise-accounts.about-recovery-codes %} 更多信息请参阅“[管理企业的恢复代码](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)”。
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ topics:
|
|||
- 您可以查看企业的审核日志。 更多信息请参阅“[访问企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)”。
|
||||
- 您可以在审核日志中搜索特定事件{% ifversion ghec %} 并导出审核日志数据{% endif %}。 更多信息请参阅“[搜索企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)”{% ifversion ghec %} 和“[导出企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)”{% endif %}。
|
||||
{%- ifversion enterprise-audit-log-ip-addresses %}
|
||||
- You can display the IP address associated with events in the audit log. For more information, see "[Displaying IP addresses in the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise)."
|
||||
- 您可以在审核日志中显示与事件关联的 IP 地址。 更多信息请参阅“[在企业的审核日志中显示 IP 地址](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise)”。
|
||||
{%- endif %}
|
||||
{%- ifversion ghec %}
|
||||
- 您可以将审核和 Git 事件数据从 {% data variables.product.prodname_dotcom %} 流式传输到外部数据管理系统。 更多信息请参阅“[流式传输企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)”。
|
||||
|
|
|
|||
|
|
@ -15,14 +15,14 @@ topics:
|
|||
|
||||
{% data reusables.enterprise.about-policies %}
|
||||
|
||||
For example, with the "Base permissions" policy, you can allow organization owners to configure the "Base permissions" policy for their organization, or you can enforce a specific base permissions level, such as "Read", for all organizations within the enterprise.
|
||||
例如，使用“基本权限”策略，您可以允许组织所有者为其组织配置“基本权限”策略，也可以为企业内的所有组织强制实施特定的基本权限级别，如“读取”。
|
||||
|
||||
By default, no enterprise policies are enforced. To identify policies that should be enforced to meet the unique requirements of your business, we recommend reviewing all the available policies in your enterprise account, starting with repository management policies. For more information, see "[Enforcing repository management polices in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)."
|
||||
默认情况下，不强制实施任何企业策略。 要确定应强制实施的策略以满足业务的独特要求，我们建议您从存储库管理策略开始，查看企业帐户中的所有可用策略。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)”。
|
||||
|
||||
While you're configuring enterprise policies, to help you understand the impact of changing each policy, you can view the current configurations for the organizations owned by your enterprise.
|
||||
在配置企业策略时，为了帮助您了解更改每个策略的影响，您可以查看企业拥有的组织的当前配置。
|
||||
|
||||
{% ifversion ghes %}
|
||||
Another way to enforce standards within your enterprise is to use pre-receive hooks, which are scripts that run on {% data variables.product.product_location %} to implement quality checks. 更多信息请参阅“[使用预接收挂钩实施策略](/admin/policies/enforcing-policy-with-pre-receive-hooks)”。
|
||||
在企业内强制实施标准的另一种方法是使用预接收挂钩，这些挂钩是在 {% data variables.product.product_location %} 上运行的脚本，用于实施质量检查。 更多信息请参阅“[使用预接收挂钩实施策略](/admin/policies/enforcing-policy-with-pre-receive-hooks)”。
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: 恢复已删除的仓库
|
||||
intro: You can restore deleted repositories to recover their contents.
|
||||
intro: 您可以恢复已删除的仓库来恢复其内容。
|
||||
permissions: Enterprise owners can restore a deleted repository.
|
||||
versions:
|
||||
ghes: '*'
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Troubleshooting license usage for GitHub Enterprise
|
||||
intro: You can troubleshoot license usage for your enterprise by auditing license reports.
|
||||
title: GitHub Enterprise 的许可证使用疑难解答
|
||||
intro: 您可以通过审核许可证报告来排查企业的许可证使用问题。
|
||||
permissions: 'Enterprise owners can review license usage for {% data variables.product.prodname_enterprise %}.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
|
|
@ -9,22 +9,22 @@ type: how_to
|
|||
topics:
|
||||
- Enterprise
|
||||
- Licensing
|
||||
shortTitle: Troubleshoot license usage
|
||||
shortTitle: 排查许可证使用问题
|
||||
---
|
||||
|
||||
## About unexpected license usage
|
||||
## 关于意外的许可证使用
|
||||
|
||||
If the number of consumed licenses for your enterprise is unexpected, you can review your consumed license report to audit your license usage across all your enterprise deployments and subscriptions. If you find errors, you can try troubleshooting steps. For more information about viewing your license usage, see "[Viewing license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" and "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
|
||||
如果企业使用的许可证数量不符合预期，可以查看已使用的许可证报告，以审核所有企业部署和订阅中的许可证使用情况。 如果发现错误，可以尝试排查步骤。 有关查看许可证使用情况的详细信息，请参阅“[查看 GitHub Enterprise 的许可证使用情况](/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)”和“[查看企业帐户的订阅和使用情况](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)”。
|
||||
|
||||
For privacy reasons, enterprise owners cannot directly access the details of user accounts.
|
||||
出于隐私原因，企业所有者无法直接访问用户帐户的详细信息。
|
||||
|
||||
## About the calculation of consumed licenses
|
||||
## 关于已用许可证的计算
|
||||
|
||||
{% data variables.product.company_short %} bills for each person who uses deployments of {% data variables.product.prodname_ghe_server %}, is a member of an organization on {% data variables.product.prodname_ghe_cloud %}, or is a {% data variables.product.prodname_vs_subscriber %}. For more information about the people in your enterprise who are counted as consuming a license, see "[About per-user pricing](/billing/managing-billing-for-your-github-account/about-per-user-pricing)."
|
||||
{% data variables.product.company_short %} 对使用 {% data variables.product.prodname_ghe_server %} 部署的每个人、{% data variables.product.prodname_ghe_cloud %} 组织的成员或 {% data variables.product.prodname_vs_subscriber %} 计费。 有关企业中计为使用许可证的人员的详细信息，请参阅“[关于每用户定价](/billing/managing-billing-for-your-github-account/about-per-user-pricing)”。
|
||||
|
||||
{% data reusables.enterprise-licensing.about-license-sync %}
|
||||
|
||||
## Fields in the consumed license files
|
||||
## 已使用的许可文件中的字段
|
||||
|
||||
The {% data variables.product.prodname_dotcom_the_website %} license usage report and {% data variables.product.prodname_ghe_server %} exported license usage file include a variety of fields to help you troubleshoot license usage for your enterprise.
|
||||
### {% data variables.product.prodname_dotcom_the_website %} license usage report (CSV file)
|
||||
|
|
@ -36,8 +36,8 @@ The license usage report for your enterprise is a CSV file that contains the fol
|
|||
| 名称 | First and last name for the user's account on GHEC. |
|
||||
| Handle or email | GHEC username, or the email address associated with the user's account on GHES. |
|
||||
| Profile link | Link to the {% data variables.product.prodname_dotcom_the_website %} profile page for the user's account on GHEC. |
|
||||
| License type | Can be one of: `Visual Studio subscription` or `Enterprise`. |
|
||||
| License status | Identifies if a user account on {% data variables.product.prodname_dotcom_the_website %} successfully matched either a {% data variables.product.prodname_vs_subscriber %} or GHES user.<br><br>Can be one of: `Matched`, `Pending Invitation`, `Server Only`, blank. |
|
||||
| License type | 可以是以下之一： `Visual Studio 订阅` 或 `Enterprise`。 |
|
||||
| 许可证状态 | Identifies if a user account on {% data variables.product.prodname_dotcom_the_website %} successfully matched either a {% data variables.product.prodname_vs_subscriber %} or GHES user.<br><br>Can be one of: `Matched`, `Pending Invitation`, `Server Only`, blank. |
|
||||
| Member roles | For each of the organizations the user belongs to on GHEC, the organization name and the person's role in that organization (`Owner` or `Member`) separated by a colon<br><br>Each organization is delimited by a comma. |
|
||||
| 企业角色 | Can be one of: `Owner` or `Member`. |
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ topics:
|
|||
|
||||
如果为编译语言设置 {% data variables.product.prodname_code_scanning %}，并且在容器化环境中构建代码，则分析可能会失败，并返回错误消息“No source code was seen during the build（在构建过程中没有看到源代码）”。 这表明 {% data variables.product.prodname_codeql %} 在代码编译过程中无法监视代码。
|
||||
|
||||
您必须在构建代码的容器中运行 {% data variables.product.prodname_codeql %}。 This applies whether you are using the {% data variables.product.prodname_codeql_cli %}{% ifversion codeql-runner-supported %}, the {% data variables.product.prodname_codeql_runner %},{% endif %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} {% ifversion codeql-runner-supported %}or the {% data variables.product.prodname_codeql_runner %}{% endif %}, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)"{% ifversion codeql-runner-supported %} or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %} for more information. 如果您使用 {% data variables.product.prodname_actions %}，请配置工作流程以在同一容器中运行所有操作。 更多信息请参阅“[示例工作流程](#example-workflow)”。
|
||||
您必须在构建代码的容器中运行 {% data variables.product.prodname_codeql %}。 无论您使用的是 {% data variables.product.prodname_codeql_cli %}{% ifversion codeql-runner-supported %}、 {% data variables.product.prodname_codeql_runner %}、{% endif %} 还是 {% data variables.product.prodname_actions %}，这都适用。 对于 {% data variables.product.prodname_codeql_cli %} {% ifversion codeql-runner-supported %}或 {% data variables.product.prodname_codeql_runner %}{% endif %}，请参阅“[在 CI 系统中安装 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)”{% ifversion codeql-runner-supported %} 或“[在 CI 系统](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)中运行 {% data variables.product.prodname_codeql_runner %}”{% endif %}以了解更多信息。 如果您使用 {% data variables.product.prodname_actions %}，请配置工作流程以在同一容器中运行所有操作。 更多信息请参阅“[示例工作流程](#example-workflow)”。
|
||||
|
||||
## 依赖项
|
||||
|
||||
|
|
|
|||
|
|
@ -127,4 +127,4 @@ topics:
|
|||
|
||||
{% data reusables.code-scanning.false-positive-fix-codeql %}
|
||||
|
||||
For more information about dismissing alerts, see {% ifversion delete-code-scanning-alerts %}"[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."{% else %} "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#dismissing--alerts)."{% endif %}
|
||||
有关消除警报的详细信息，请参阅 {% ifversion delete-code-scanning-alerts %}“[管理存储库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)”。{% else %} “[管理存储库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#dismissing--alerts)”。{% endif %}
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ Dependabot 执行扫描以检测有漏洞的依赖项，并在将新漏洞添加
|
|||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. Under "Code security and analysis", to the right of {% data variables.product.prodname_dependabot_alerts %}, click **Enable** to enable alerts or **Disable** to disable alerts. 
|
||||
1. 在“Code security and analysis（代码安全和分析）”下，在 {% data variables.product.prodname_dependabot_alerts %} 的右侧，单击 **Enable（启用）**以启用警报，或单击 **Disable（禁用）**禁用警报。 
|
||||
{% endif %}{% ifversion ghes or ghae %}
|
||||
|
||||
您的企业所有者可以启用或禁用存储库的 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[为企业启用 Dependabot](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ shortTitle: 配置 dependabot.yml
|
|||
|
||||
*dependabot.yml* 文件有两个必需的顶级密钥：`version` 和 `updates`。 您可以选择包括顶级 `registries` 密钥{% ifversion fpt or ghec or ghes > 3.4 %} 和/或 `enable-beta-ecosystems` 密钥{% endif %}。 该文件必须以 `version: 2` 开头。
|
||||
|
||||
## Configuration options for the *dependabot.yml* file
|
||||
## *dependabot.yml* 文件的配置选项
|
||||
|
||||
顶级 `updates` 密钥是必需的。 您使用它来配置 {% data variables.product.prodname_dependabot %} 如何更新版本或项目的依赖项。 每个条目都为特定的包管理器配置更新设置。 您可以使用以下选项。
|
||||
|
||||
|
|
@ -57,7 +57,7 @@ shortTitle: 配置 dependabot.yml
|
|||
|
||||
仅对默认分支上有漏洞的包清单提出安全更新。 如果为同一分支设置配置选项（不使用 `target-branch` 时为 true），并为有漏洞的清单指定 `package-ecosystem` 和 `directory`，则安全更新的拉取请求使用相关选项。
|
||||
|
||||
一般而言，安全更新会使用影响拉取请求的任何配置选项，例如添加元数据或改变其行为。 For more information about security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
|
||||
一般而言，安全更新会使用影响拉取请求的任何配置选项，例如添加元数据或改变其行为。 有关安全更新的更多信息，请参阅“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)”。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
|
@ -292,7 +292,7 @@ updates:
|
|||
|
||||
您可以搜索仓库中是否有 `"@dependabot ignore" in:comments`，以检查仓库是否存储了 `ignore` 首选项。 如果您希望取消忽略以这种方式忽略的依赖项，请重新打开拉取请求。
|
||||
|
||||
For more information about the `@dependabot ignore` commands, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
|
||||
有关 `@dependabot ignore` 命令的更多信息，请参阅“[管理依赖关系更新的拉取请求](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)”。
|
||||
|
||||
#### 指定要忽略的依赖项和版本
|
||||
|
||||
|
|
|
|||
|
|
@ -35,15 +35,15 @@ shortTitle: 配置版本更新
|
|||
|
||||
## 启用 {% data variables.product.prodname_dependabot_version_updates %}
|
||||
|
||||
You enable {% data variables.product.prodname_dependabot_version_updates %} by commiting a *dependabot.yml* configuration file to your repository.
|
||||
{% ifversion dependabot-settings-update-37 %}If you enable the feature in your settings page, GitHub creates a basic file which you can edit, otherwise you can create the file using any file editor.
|
||||
通过将 *dependabot.yml* 配置文件提交到仓库，可启用 {% data variables.product.prodname_dependabot_version_updates %}。
|
||||
{% ifversion dependabot-settings-update-37 %}如果在设置页面中启用该功能，GitHub 会创建一个可以编辑的基本文件，否则您可以使用任何文件编辑器创建该文件。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot_version_updates %}", click **Enable** to open a basic *dependabot.yml* configuration file in the `.github` directory of your repository.
|
||||
1. 在“Code security and analysis（代码安全性和分析）”下的“{% data variables.product.prodname_dependabot_version_updates %}”右侧，单击 **Enable（启用）**以打开存储库的 `.github` 目录中的基本 *dependabot.yml* 配置文件。
|
||||
{% else %}
|
||||
1. Create a *dependabot.yml* configuration file in the `.github` directory of your repository.
|
||||
1. 在存储库的 `.github` 目录中创建一个 *dependabot.yml* 配置文件。
|
||||
{% endif %}
|
||||
1. 添加 `version`。
|
||||
1. （可选）如果您在私人注册表中包含依赖项，请添加包含身份验证详细信息的 `registries` 部分。
|
||||
|
|
@ -54,7 +54,7 @@ You enable {% data variables.product.prodname_dependabot_version_updates %} by c
|
|||
- `schedule.interval` 指定检查新版本的频率。
|
||||
{% data reusables.dependabot.check-in-dependabot-yml %}
|
||||
|
||||
For information about all the configuration options, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates)."
|
||||
有关所有配置选项的信息，请参阅“[dependabot.yml 文件的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates)”。
|
||||
|
||||
### 示例 *dependabot.yml* 文件
|
||||
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ topics:
|
|||
{% endif %}
|
||||
|
||||
{% ifversion ghes > 3.2 or ghae %}
|
||||
除了代码，您可能还需要在其他地方使用机密。 For example, to allow {% data variables.product.prodname_actions %} workflows{% ifversion ghes %} or {% data variables.product.prodname_dependabot %}{% endif %} to communicate with other systems. For more information on how to securely store and use secrets, see "[Encrypted secrets in Actions](/actions/security-guides/encrypted-secrets){% ifversion ghes %}" and "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."{% else %}."{% endif %}
|
||||
除了代码，您可能还需要在其他地方使用机密。 例如，允许 {% data variables.product.prodname_actions %} 工作流程、{% ifversion ghes %} 或 {% data variables.product.prodname_dependabot %}{% endif %} 与其他系统进行通信。 有关如何安全地存储和使用机密的详细信息，请参阅“[Actions 中的加密机密](/actions/security-guides/encrypted-secrets){% ifversion ghes %}”和“[管理 Dependabot 的加密机密](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)”。{% else %}”。{% endif %}
|
||||
{% endif %}
|
||||
|
||||
## 将有漏洞的编码模式排除在存储库之外
|
||||
|
|
|
|||
|
|
@ -1,9 +1,36 @@
|
|||
---
|
||||
title: GitHub Desktop 文档
|
||||
title: GitHub Desktop
|
||||
shortTitle: GitHub Desktop
|
||||
intro: 设置和使用 GitHub Desktop 管理项目工作的分步指南
|
||||
intro: 'With GitHub Desktop, you can interact with GitHub using a GUI instead of the command line or a web browser. You can use GitHub Desktop to complete most Git commands from your desktop, such as pushing to, pulling from, and cloning remote repositories, attributing commits, and creating pull requests, with visual confirmation of changes.'
|
||||
introLinks:
|
||||
overview: /desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop
|
||||
featuredLinks:
|
||||
guides:
|
||||
- /desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop
|
||||
- /desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop
|
||||
- /desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github
|
||||
guideCards:
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/stashing-changes
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/managing-commits/amending-a-commit
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit
|
||||
popular:
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/managing-commits
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github
|
||||
changelog:
|
||||
label: desktop
|
||||
versions:
|
||||
fpt: '*'
|
||||
layout: product-landing
|
||||
versions:
|
||||
fpt: '*'
|
||||
topics:
|
||||
- Desktop
|
||||
- Repositories
|
||||
children:
|
||||
- /installing-and-configuring-github-desktop
|
||||
- /contributing-and-collaborating-using-github-desktop
|
||||
|
|
|
|||
|
|
@ -0,0 +1,30 @@
|
|||
---
|
||||
title: About GitHub Community Exchange
|
||||
intro: 'As a student, learn the skills you need to contribute to open source projects and grow your own portfolio, with {% data variables.product.prodname_community_exchange %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: Community Exchange
|
||||
---
|
||||
|
||||
## 关于 {% data variables.product.prodname_community_exchange %}
|
||||
|
||||
{% data variables.product.prodname_community_exchange %} is a student community within the {% data variables.product.prodname_global_campus %} portal. As a student, it's a place where you can get exposure for your project and discover other student repositories in need of collaborators and maintainers.
|
||||
|
||||
|
||||
|
||||
You can help your peers learn open source skills, become a project maintainer, and grow your {% data variables.product.prodname_dotcom %} portfolio and network within a safe and verified community platform.
|
||||
|
||||
{% data variables.product.prodname_community_exchange %} allows you to:
|
||||
- Discover student created repositories
|
||||
- Star repositories of interest
|
||||
- Submit a repository in need of collaborators
|
||||
- Submit a repository to teach new skills
|
||||
- Manage your repository submissions
|
||||
|
||||
To access {% data variables.product.prodname_community_exchange %}, visit your {% data variables.product.prodname_global_campus %} dashboard at https://education.github.com.
|
||||
|
||||
If you're a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_community_exchange %} within {% data variables.product.prodname_global_campus %}.
|
||||
|
||||
- If you’re a student and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [student application form](https://education.github.com/discount_requests/student_application). For more information, see "[About GitHub Education for students](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students)."
|
||||
|
||||
- If you’re an educator and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [teacher application form](https://education.github.com/discount_requests/teacher_application). For more information, see "[About GitHub Education for educators](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount)."
|
||||
|
|
@ -22,3 +22,4 @@ shortTitle: 适合学生
|
|||
## 延伸阅读
|
||||
|
||||
- "[关于教育者和研究人员版 {% data variables.product.prodname_education %}](/articles/about-github-education-for-educators-and-researchers)"
|
||||
- "[关于 {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)"
|
||||
|
|
|
|||
|
|
@ -11,6 +11,7 @@ children:
|
|||
- /about-github-education-for-students
|
||||
- /apply-for-a-student-developer-pack
|
||||
- /why-wasnt-my-application-for-a-student-developer-pack-approved
|
||||
- /about-github-community-exchange
|
||||
shortTitle: 用于功课
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ The {% data variables.product.prodname_codespaces %} Education benefit gives ver
|
|||
|
||||
To become a verified teacher, you need to be approved for an educator or teacher benefit. For more information, see "[Applying for an educator or teacher benefit](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount#applying-for-an-educator-or-researcher-discount)."
|
||||
|
||||
After you have confirmation that you are a verified teacher, visit [Global Campus for Teachers](https://education.github.com/globalcampus/teacher) to upgrade the organization to GitHub Team. For more information, see [GitHub's products](/get-started/learning-about-github/githubs-products#github-team).
|
||||
After you have confirmation that you are a verified teacher, visit [{% data variables.product.prodname_global_campus %} for Teachers](https://education.github.com/globalcampus/teacher) to upgrade the organization to GitHub Team. For more information, see [GitHub's products](/get-started/learning-about-github/githubs-products#github-team).
|
||||
|
||||
If you are eligible for the {% data variables.product.prodname_codespaces %} Education benefit, when you enable {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_classroom %} for your organization, GitHub automatically adds a Codespace policy to restrict machine types for all codespaces in the organization to 2 core machines. This helps you make the most of the free {% data variables.product.prodname_codespaces %} usage. However, you can change or remove these policies in your organization settings. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: 恢复已删除的仓库
|
||||
intro: '{% ifversion ghes or ghae %}An enterprise owner{% elsif fpt or ghec %}You{% endif %} can restore some deleted repositories to recover their contents.'
|
||||
intro: '{% ifversion ghes or ghae %}企业所有者{% elsif fpt or ghec %}您{% endif %} 可以还原某些已删除的存储库以恢复其内容。'
|
||||
permissions: '{% ifversion ghes or ghae %}{% elsif fpt or ghec %}Anyone can restore deleted repositories that were owned by their own personal account. Organization owners can restore deleted repositories that were owned by the organization.{% endif %}'
|
||||
redirect_from:
|
||||
- /articles/restoring-a-deleted-repository
|
||||
|
|
@ -18,7 +18,7 @@ shortTitle: 恢复已删除的仓库
|
|||
|
||||
{% ifversion ghes or ghae %}
|
||||
|
||||
Usually, deleted repositories can be restored within 90 days by an enterprise owner{% ifversion ghes %} on {% data variables.product.product_location %}{% endif %}. 更多信息请参阅“[恢复删除的仓库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。
|
||||
通常，{% ifversion ghes %}{% data variables.product.product_location %}上{% endif %}已删除的存储库可以在 90 天内由企业所有者恢复。 更多信息请参阅“[恢复删除的仓库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。
|
||||
|
||||
{% else %}
|
||||
|
||||
|
|
|
|||
|
|
@ -29,11 +29,11 @@ miniTocMaxHeadingLevel: 3
|
|||
|
||||
您可以对您的仓库启用 {% data variables.product.prodname_actions %}。 {% data reusables.actions.enabled-actions-description %} 您可以对您的仓库完全禁用 {% data variables.product.prodname_actions %}。 {% data reusables.actions.disabled-actions-description %}
|
||||
|
||||
Alternatively, you can enable {% data variables.product.prodname_actions %} in your repository but limit the actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} a workflow can run.
|
||||
或者，您也可以在存储库中启用 {% data variables.product.prodname_actions %}，但限制工作流程可以运行的操作{% ifversion actions-workflow-policy %}和可重用工作流程{% endif %}。
|
||||
|
||||
## 管理仓库的 {% data variables.product.prodname_actions %} 权限
|
||||
|
||||
You can disable {% data variables.product.prodname_actions %} for a repository, or set a policy that configures which actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} can be used in the repository.
|
||||
您可以禁用存储库的 {% data variables.product.prodname_actions %} ，或设置策略来配置可在存储库中使用的 {% ifversion actions-workflow-policy %} 和可重用工作流{% endif %} 。
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
@ -147,7 +147,7 @@ You can disable {% data variables.product.prodname_actions %} for a repository,
|
|||
|
||||
企业成员可以使用内部存储库来处理项目，而无需公开共享信息。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)”。
|
||||
|
||||
You can use the steps below to configure whether {% ifversion internal-actions%}actions and {% endif %}workflows in an internal repository can be accessed from outside the repository.{% ifversion internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)." 或者，您可以使用 REST API 来设置或获取访问级别的详细信息。 更多信息请参阅“[获取存储库外部工作流程的访问级别](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#get-the-level-of-access-for-workflows-outside-of-the-repository)”和“[设置存储库外部工作流程的访问级别](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#set-the-level-of-access-for-workflows-outside-of-the-repository)”。{% endif %}
|
||||
您可以使用以下步骤配置是否可以从存储库外部访问内部存储库中的 {% ifversion internal-actions%}操作和 {% endif %}工作流程。{% ifversion internal-actions %} 更多信息请参阅“[与企业共享操作和工作流程](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)”。 或者，您可以使用 REST API 来设置或获取访问级别的详细信息。 更多信息请参阅“[获取存储库外部工作流程的访问级别](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#get-the-level-of-access-for-workflows-outside-of-the-repository)”和“[设置存储库外部工作流程的访问级别](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#set-the-level-of-access-for-workflows-outside-of-the-repository)”。{% endif %}
|
||||
|
||||
1. 在 {% data variables.product.prodname_dotcom %} 上，导航到内部仓库的主页面。
|
||||
1. 在仓库名称下，单击 {% octicon "gear" aria-label="The gear icon" %}**Settings（设置）**。
|
||||
|
|
|
|||
|
|
@ -14,4 +14,4 @@ versions:
|
|||
|
||||
## 关于权限 API
|
||||
|
||||
The {% data variables.product.prodname_actions %} Permissions API allows you to set permissions for what enterprises, organizations, and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} are allowed to run.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."{% endif %}
|
||||
{% data variables.product.prodname_actions %} 权限 API 可让您设置权限，允许哪些企业、组织和存储库运行 {% data variables.product.prodname_actions %}，以及允许哪些操作{% ifversion actions-workflow-policy %} 和可重用工作流程{% endif %}运行。{% ifversion fpt or ghec or ghes %} 更多信息请参阅“[使用限制、计费和管理](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)”。{% endif %}
|
||||
|
|
|
|||
|
|
@ -29,9 +29,12 @@ HTTP/2 200
|
|||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" xml:lang="en-US">
|
||||
<feed xmlns="http://www.w3.org/2005/Atom"
|
||||
xmlns:media="http://search.yahoo.com/mrss/"
|
||||
xml:lang="en-US">
|
||||
<id>tag:github.com,2008:/security-advisories</id>
|
||||
<link rel="self" type="application/atom+xml" href="https://github.com/security-advisories.atom"/>
|
||||
<link rel="self" type="application/atom+xml"
|
||||
href="https://github.com/security-advisories.atom"/>
|
||||
<title>GitHub Security Advisory Feed</title>
|
||||
<author>
|
||||
<name>GitHub</name>
|
||||
|
|
@ -41,10 +44,18 @@ HTTP/2 200
|
|||
<id>tag:github.com,2008:GHSA-abcd-12ab-23cd</id>
|
||||
<published>2018-07-26T15:14:52Z</published>
|
||||
<updated>2019-01-14T19:34:52Z</updated>
|
||||
<title type="html">[GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp</title>
|
||||
<title type="html">[GHSA-abcd-12ab-23cd] Moderate
|
||||
severity vulnerability that affects Octoapp</title>
|
||||
<category term="NPM"/>
|
||||
<content type="html">
|
||||
<p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p>
|
||||
<p>Octoapp node module before 4.17.5 suffers
|
||||
from a Modification of Assumed-Immutable Data (MAID)
|
||||
vulnerability via defaultsDeep, merge, and mergeWith
|
||||
functions, which allows a malicious user to modify
|
||||
the prototype of "Object" via
|
||||
<strong>proto</strong>, causing the
|
||||
addition or modification of an existing property
|
||||
that will exist on all objects.</p>
|
||||
<p><strong>Affected Packages</strong></p>
|
||||
|
||||
<dl>
|
||||
|
|
|
|||
|
|
@ -317,6 +317,6 @@ CCPA 为加州居民提供关于其个人信息的某些权利。 要提交基
|
|||
您可以书面或通过授权书指定授权代理人代表您提出请求，以行使您在 CCPA 下的权利。 在接受代理商的此类请求之前，我们将要求代理商提供您授权其代表您行事的证明，并且我们可能需要您直接向我们验证您的身份。 此外，要提供或删除特定的个人信息，我们需要在法律要求的确定程度上验证您的身份。 我们将通过要求您从与您的帐户关联的电子邮件地址提交请求，或要求您提供验证帐户所需的信息，以验证您的请求。 [请注意，您可以在 GitHub 帐户中使用双因素身份验证。](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication)
|
||||
最后，您有权在收集个人信息时或之前收到有关我们做法的通知。
|
||||
|
||||
此外，根据《加利福尼亚州民法典》第 1798.83 条（也称为“闪耀之光”法律），出于个人、家族或家庭目的向与该个人建立业务关系的企业提供个人信息的加利福尼亚州居民（“加州客户”），可以要求提供有关该企业是否已出于第三方的直接营销目的向任何第三方披露个人信息的信息。 请注意，我们不会向任何第三方披露个人信息，以用于本法规定的直接营销目的。 加州客户可以通过发送电子邮件到 **(privacy [at] github [dot] com)**索取有关我们遵守本法律的更多信息。 Please note that businesses are required to respond to one request per California Customer each year and may not be required to respond to requests made by means other than through the designated email address.
|
||||
此外，根据《加利福尼亚州民法典》第 1798.83 条（也称为“闪耀之光”法律），出于个人、家族或家庭目的向与该个人建立业务关系的企业提供个人信息的加利福尼亚州居民（“加州客户”），可以要求提供有关该企业是否已出于第三方的直接营销目的向任何第三方披露个人信息的信息。 请注意，我们不会向任何第三方披露个人信息，以用于本法规定的直接营销目的。 加州客户可以通过发送电子邮件到 **(privacy [at] github [dot] com)**索取有关我们遵守本法律的更多信息。 请注意，企业每年必须回复每位加州客户的一个请求，并且可能不需要回复通过指定电子邮件地址以外的方式提出的请求。
|
||||
|
||||
California residents under the age of 18 who are registered users of online sites, services, or applications have a right under California Business and Professions Code Section 22581 to remove, or request and obtain removal of, content or information they have publicly posted. To remove content or information you have publicly posted, [please submit a Private Information Removal request](https://support.github.com/contact/private-information). Alternatively, to request that we remove such content or information, please send a detailed description of the specific content or information you wish to have removed to [GitHub support](https://support.github.com/contact). Please be aware that your request does not guarantee complete or comprehensive removal of content or information posted online and that the law may not permit or require removal in certain circumstances. If you have any questions about our privacy practices with respect to California residents, please contact us via our [contact form](https://support.github.com/contact?tags=docs-policy).
|
||||
根据《加利福尼亚州商业和职业法典》第 22581 条，未满 18 周岁的加利福尼亚州居民是在线网站、服务或应用程序的注册用户，他们有权删除、请求和获取他们公开发布的内容或信息。 要删除您公开发布的内容或信息， [请提交私人信息删除请求](https://support.github.com/contact/private-information)。 或者，要请求我们删除此类内容或信息，请将您希望删除的特定内容或信息的详细说明发送到 [GitHub 支持](https://support.github.com/contact)。 请注意，您的请求并不能保证完全或全面删除在线发布的内容或信息，并且在某些情况下，法律可能不允许或要求删除。 如果您对我们对加州居民的隐私惯例有任何疑问，请通过我们的[联系表格](https://support.github.com/contact?tags=docs-policy)与我们联系。
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ GitHub 在如何使用您的数据、如何收集您的数据以及与谁分享
|
|||
|
||||
## GitHub 子处理商
|
||||
|
||||
我们与第三方子处理商（例如我们的供应商和服务提供商）分享您的信息时，我们仍对您的信息负责。 我们在引入新供应商时，会竭尽所能保持您的信任，并且要求所有供应商与我们签订数据保护协议，以约束他们对用户个人信息（定义见[隐私声明](/articles/github-privacy-statement/)）的处理。 You can sign up to receive subprocessor list updates [here](https://www.github.com/privacy/subprocessors).
|
||||
我们与第三方子处理商（例如我们的供应商和服务提供商）分享您的信息时，我们仍对您的信息负责。 我们在引入新供应商时，会竭尽所能保持您的信任，并且要求所有供应商与我们签订数据保护协议，以约束他们对用户个人信息（定义见[隐私声明](/articles/github-privacy-statement/)）的处理。 您可以在[此处](https://www.github.com/privacy/subprocessors)注册以接收子处理器列表更新。
|
||||
|
||||
| 子处理商名称 | 处理说明 | 处理地点 | 公司地点 |
|
||||
|:------------------------ |:----------------- |:---- |:---- |
|
||||
|
|
|
|||
|
|
@ -0,0 +1,7 @@
|
|||
---
|
||||
#Issue #7062
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-7062'
|
||||
|
|
@ -9,6 +9,7 @@ sections:
|
|||
- SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog.
|
||||
- For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out.
|
||||
- When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified.
|
||||
- 'The Releases page would return a 500 error when the repository has tags that contain non-ASCII characters. [Updated: 2022-06-10]'
|
||||
changes:
|
||||
- In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.
|
||||
- When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not supported.
|
||||
|
|
|
|||
|
|
@ -12,6 +12,7 @@ sections:
|
|||
- Videos uploaded to issue comments would not be rendered properly.
|
||||
- When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified.
|
||||
- When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests.
|
||||
- 'The Releases page would return a 500 error when the repository has tags that contain non-ASCII characters. [Updated: 2022-06-10]'
|
||||
changes:
|
||||
- In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.
|
||||
- When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported.
|
||||
|
|
|
|||
|
|
@ -15,6 +15,7 @@ sections:
|
|||
- When using the file finder on a repository page, typing the backspace key within the search field would result in search results being listed multiple times and cause rendering problems.
|
||||
- When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events.
|
||||
- When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests.
|
||||
- 'The Releases page would return a 500 error when the repository has tags that contain non-ASCII characters. [Updated: 2022-06-10]'
|
||||
changes:
|
||||
- In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.
|
||||
- When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported.
|
||||
|
|
|
|||
|
|
@ -18,6 +18,7 @@ sections:
|
|||
- Videos uploaded to issue comments would not be rendered properly.
|
||||
- When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events.
|
||||
- When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests.
|
||||
- 'The Releases page would return a 500 error when the repository has tags that contain non-ASCII characters. [Updated: 2022-06-10]'
|
||||
changes:
|
||||
- In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.
|
||||
- The Nomad allocation timeout for Dependency Graph has been increased to ensure post-upgrade migrations can complete.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,6 @@
|
|||
Reusable workflows from public repositories can be referenced using a SHA, a release tag, or a branch name. For more information, see ["Calling a reusable workflow"](/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow).
|
||||
|
||||
When you re-run a workflow that uses a reusable workflow and the reference is not a SHA, there are some behaviors to be aware of:
|
||||
|
||||
* Re-running all jobs in a workflow will use the reusable workflow from the specified reference. For more information about re-running all jobs in a workflow, see ["Re-running all the jobs in a workflow"](/actions/managing-workflow-runs/re-running-workflows-and-jobs#re-running-all-the-jobs-in-a-workflow).
|
||||
* Re-running failed jobs or a specific job in a workflow will use the reusable workflow from the same commit SHA of the first attempt. For more information about re-running failed jobs in a workflow, see ["Re-running failed jobs in a workflow"](/actions/managing-workflow-runs/re-running-workflows-and-jobs#re-running-failed-jobs-in-a-workflow). For more information about re-running a specific job in a workflow, see ["Re-running a specific job in a workflow"](/actions/managing-workflow-runs/re-running-workflows-and-jobs#re-running-a-specific-job-in-a-workflow).
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
作为经认可的教育机构的学生或教职员工，您可以申请 GitHub Education 福利，其中包括访问 GitHub 全球校园。 全球校园是一个门户，允许 GitHub 教育社区在一个位置访问其教育福利！ 全球校园门户包括访问 GitHub 教育社区、专业开发人员使用的行业工具、活动、[校园电视](https://www.twitch.tv/githubeducation) 内容、GitHub Classroom 及其他独家功能，以帮助学生和教师塑造下一代软件开发。
|
||||
As a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_global_campus %}. {% data variables.product.prodname_global_campus %} is a portal that allows the GitHub Education Community to access their education benefits—all in one place! The {% data variables.product.prodname_global_campus %} portal includes access to {% data variables.product.prodname_education_community_with_url %}, industry tools used by professional developers, events, [Campus TV](https://www.twitch.tv/githubeducation) content, {% data variables.product.prodname_classroom_with_url %}, and other exclusive features to help students and teachers shape the next generation of software development.
|
||||
|
||||
在申请个人折扣之前，请检查您的学习社区是否已作为 {% data variables.product.prodname_campus_program %} 学校与我们合作。 更多信息请参阅“[关于 {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)”。
|
||||
|
|
|
|||
|
|
@ -45,6 +45,8 @@ prodname_classroom: 'GitHub 课堂'
|
|||
prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)'
|
||||
prodname_campus_program: 'GitHub 校园计划'
|
||||
prodname_student_pack: 'GitHub Student Developer Pack'
|
||||
prodname_global_campus: 'GitHub Global Campus'
|
||||
prodname_community_exchange: 'GitHub Community Exchange'
|
||||
#GitHub CLI
|
||||
prodname_cli: 'GitHub CLI'
|
||||
#GitHub Desktop
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче