New translation batch for cn (#27728)
* 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 Co-authored-by: Grace Park <gracepark@github.com>
This commit is contained in:
docubot
@@ -294,6 +294,7 @@ translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml,Listed in loc
|
||||
translations/zh-CN/data/release-notes/enterprise-server/2-22/22.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-0/0.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-0/16.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-1/1.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-1/10.yml,broken liquid tags
|
||||
@@ -317,6 +318,7 @@ translations/zh-CN/data/release-notes/enterprise-server/3-1/8.yml,broken liquid
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-1/9.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/github-ae/2021-03/2021-03-03.yml,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/actions-use-policy-settings.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags
|
||||
|
||||
|
@@ -1051,7 +1051,7 @@ on:
|
||||
|
||||
{% endnote %}
|
||||
|
||||
在存储库中发生发布活动时运行工作流程。 有关发行版 API 的信息，请参阅 GraphQL API 文档中的“[发行版](/graphql/reference/objects#release)”或 REST API 文档中的“[发行版](/rest/reference/repos#releases)”。
|
||||
在存储库中发生发布活动时运行工作流程。 有关发行版 API 的信息，请参阅 GraphQL API 文档中的“[发行版](/graphql/reference/objects#release)”或 REST API 文档中的“[发行版](/rest/reference/releases)”。
|
||||
|
||||
例如，您可以在版本发布为 `published` 时运行工作流程。
|
||||
|
||||
|
||||
@@ -673,6 +673,12 @@ This utility manually repackages a repository network to optimize pack storage.
|
||||
|
||||
You can add the optional `--prune` argument to remove unreachable Git objects that aren't referenced from a branch, tag, or any other ref. This is particularly useful for immediately removing [previously expunged sensitive information](/enterprise/user/articles/remove-sensitive-data/).
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Before using the `--prune` argument to remove unreachable Git objects, put {% data variables.product.product_location %} into maintenance mode, or ensure the repository is offline. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
```shell
|
||||
ghe-repo-gc <em>username</em>/<em>reponame</em>
|
||||
```
|
||||
|
||||
@@ -33,12 +33,13 @@ topics:
|
||||
|
||||
## 配置存储库缓存
|
||||
|
||||
1. 在测试期间，您必须为主 {% data variables.product.prodname_ghe_server %} 设备上的存储库缓存启用功能标志。
|
||||
{% ifversion ghes = 3.3 %}
|
||||
1. On your primary {% data variables.product.prodname_ghe_server %} appliance, enable the feature flag for repository caching.
|
||||
|
||||
```
|
||||
$ ghe-config cluster.cache-enabled true
|
||||
```
|
||||
|
||||
{%- endif %}
|
||||
1. 在所需平台上设置新的 {% data variables.product.prodname_ghe_server %} 设备。 此设备将是您的存储库缓存。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)”。
|
||||
{% data reusables.enterprise_installation.replica-steps %}
|
||||
1. 使用 SSH 连接到存储库缓存的 IP 地址。
|
||||
@@ -46,7 +47,13 @@ topics:
|
||||
```shell
|
||||
$ ssh -p 122 admin@<em>REPLICA IP</em>
|
||||
```
|
||||
{%- ifversion ghes = 3.3 %}
|
||||
1. On your cache replica, enable the feature flag for repository caching.
|
||||
|
||||
```
|
||||
$ ghe-config cluster.cache-enabled true
|
||||
```
|
||||
{%- endif %}
|
||||
{% data reusables.enterprise_installation.generate-replication-key-pair %}
|
||||
{% data reusables.enterprise_installation.add-ssh-key-to-primary %}
|
||||
1. 要验证与主缓存的连接并为存储库缓存启用副本模式，请再次运行 `ghe-repl-setup`。
|
||||
|
||||
@@ -27,12 +27,22 @@ You can access your resources in {% data variables.product.product_name %} in a
|
||||
|
||||
## Authenticating in your browser
|
||||
|
||||
You can authenticate to {% data variables.product.product_name %} in your browser {% ifversion ghae %}using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}in different ways.
|
||||
{% ifversion ghae %}
|
||||
|
||||
You can authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
|
||||
|
||||
{% else %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
- If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
||||
If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also be required to enable two-factor authentication.
|
||||
If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
||||
If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also use two-factor authentication and SAML single sign-on, which can be required by organization and enterprise owners.
|
||||
|
||||
{% else %}
|
||||
|
||||
You can authenticate to {% data variables.product.product_name %} in your browser in a number of ways.
|
||||
|
||||
{% endif %}
|
||||
|
||||
- **Username and password only**
|
||||
@@ -42,9 +52,12 @@ You can authenticate to {% data variables.product.product_name %} in your browse
|
||||
After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the GitHub Mobile application installed, you'll receive a notification there instead.{% endif %}
|
||||
- **Two-factor authentication (2FA)** (recommended)
|
||||
- If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)."
|
||||
- In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% endif %}{% ifversion ghes %}
|
||||
- **Identity provider (IdP) authentication**
|
||||
- Your site administrator may configure {% data variables.product.product_location %} to use authentication with an IdP instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)."
|
||||
- In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% ifversion ghes %}
|
||||
- **External authentication**
|
||||
- Your site administrator may configure {% data variables.product.product_location %} to use external authentication instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)."{% endif %}{% ifversion fpt or ghec %}
|
||||
- **SAML single sign-on**
|
||||
- Before you can access resources owned by an organization or enterprise account that uses SAML single sign-on, you may need to also authenticate through an IdP. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Authenticating with {% data variables.product.prodname_desktop %}
|
||||
|
||||
@@ -24,9 +24,9 @@ You can remove the file from the latest commit with `git rm`. For information on
|
||||
|
||||
{% warning %}
|
||||
|
||||
This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, it's important to note that those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}.
|
||||
**Warning**: This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}.
|
||||
|
||||
**Warning: Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! If you committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history.
|
||||
**Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! If you committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -151,7 +151,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
|
||||
|
||||
After using either the BFG tool or `git filter-repo` to remove the sensitive data and pushing your changes to {% data variables.product.product_name %}, you must take a few more steps to fully remove the data from {% data variables.product.product_name %}.
|
||||
|
||||
1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed.
|
||||
1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed.{% ifversion ghes %} For more information about how site administrators can remove unreachable Git objects, see "[Command line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)."{% endif %}
|
||||
|
||||
2. Tell your collaborators to [rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *not* merge, any branches they created off of your old (tainted) repository history. One merge commit could reintroduce some or all of the tainted history that you just went to the trouble of purging.
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ shortTitle: 更改 2FA 递送方式
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.security %}
|
||||
3. Next to "Primary two-factor method", click **Change**. 
|
||||
3. 在“Primary two-factor method（主要双重方法）”旁边，点击 **Change（更改）**。 
|
||||
4. 在“Delivery options（递送选项）”下，单击 **Reconfigure two-factor authentication（重新配置双重身份验证）**。 
|
||||
5. 决定是使用 TOTP 移动应用程序还是使用短信设置双重身份验证。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication)”。
|
||||
- 要使用 TOTP 移动应用程序设置双重身份验证，请单击 **Set up using an app（使用应用程序设置）**。
|
||||
|
||||
@@ -35,7 +35,7 @@ topics:
|
||||
{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %}
|
||||
1. 如果未启用“{% data variables.product.prodname_GH_advanced_security %}”，请单击该功能旁边的 **Enable（启用）**。 
|
||||
|
||||
{% elsif ghes or ghae %}
|
||||
{% elsif ghes %}
|
||||
为 {% data variables.product.product_location %} 启用依赖关系图并为组织或仓库启用{% data variables.product.prodname_advanced_security %} 时，依赖项审查可用。 更多信息请参阅“[为企业启用 {% data variables.product.prodname_GH_advanced_security %}](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)”。
|
||||
|
||||
### 检查是否启用了依赖关系图
|
||||
|
||||
@@ -25,7 +25,7 @@ shortTitle: 配置依赖关系图
|
||||
{% ifversion fpt or ghec %} ## About configuring the dependency graph {% endif %}
|
||||
{% ifversion fpt or ghec %}要生成依赖关系图，{% data variables.product.product_name %} 需要对仓库的依赖项清单和锁定文件的只读访问权限。 依赖关系图自动为所有公共仓库生成，您可以选择为私有仓库启用它。 有关查看依赖关系图的更多信息，请参阅“[探索存储库的依赖关系](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)”。{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %} ## Enabling the dependency graph
|
||||
{% ifversion ghes %} ## Enabling the dependency graph
|
||||
{% data reusables.dependabot.ghes-ghae-enabling-dependency-graph %}{% endif %}{% ifversion fpt or ghec %}
|
||||
|
||||
### 为私有仓库启用或禁用依赖关系图
|
||||
|
||||
@@ -19,7 +19,9 @@ shortTitle: 分配议题和 PR
|
||||
|
||||
## 关于议题和拉取请求受理人
|
||||
|
||||
每个议题和拉取请求最多可分配给 10 个人，包括您自己、 任何评论了议题或拉取请求的人、任何对仓库有写入权限的人以及对仓库有读取权限的组织成员 。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/articles/access-permissions-on-github)”。
|
||||
You can assign multiple people to each issue or pull request, including yourself, anyone who has commented on the issue or pull request, anyone with write permissions to the repository, and organization members with read permissions to the repository. 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/articles/access-permissions-on-github)”。
|
||||
|
||||
Issues and pull requests in public repositories, and in private repositories for a paid account, can have up to 10 people assigned. Private repositories on the free plan are limited to one person per issue or pull request.
|
||||
|
||||
## 分配单个议题或拉取请求
|
||||
|
||||
|
||||
@@ -5,8 +5,6 @@ permissions: Organization owners can export member information for their organiz
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.3'
|
||||
ghae: issue-5146
|
||||
topics:
|
||||
- Organizations
|
||||
- Teams
|
||||
|
||||
@@ -2,8 +2,6 @@
|
||||
title: 管理组织中的安全管理员
|
||||
intro: 通过将团队分配给安全管理员角色，您可以为安全团队提供他们对组织所需的最少访问权限。
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>=3.3'
|
||||
feature: security-managers
|
||||
topics:
|
||||
- Organizations
|
||||
@@ -30,7 +28,7 @@ permissions: Organization owners can assign the security manager role.
|
||||
其他功能（包括组织的安全概述）在将 {% data variables.product.prodname_ghe_cloud %} 与 {% data variables.product.prodname_advanced_security %} 一起使用的组织中可用。 更多信息请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)。
|
||||
{% endif %}
|
||||
|
||||
如果团队具有安全管理员角色，则对团队和特定存储库具有管理员访问权限的人员可以更改团队对该存储库的访问级别，但不能删除访问权限。 更多信息请参阅“[管理团队对组织存储库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion ghes %}”。{% else %} 和“[管理可以访问存储库的团队和人员](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)”。{% endif %}
|
||||
如果团队具有安全管理员角色，则对团队和特定存储库具有管理员访问权限的人员可以更改团队对该存储库的访问级别，但不能删除访问权限。 For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %}" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% else %}."{% endif %}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -48,7 +48,7 @@ topics:
|
||||
您可以查看依赖项图的 **Dependents（依赖项）**选项卡，了解哪些仓库和包依赖于您仓库中的代码，并因此可能受到新发行版的影响。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。
|
||||
{% endif %}
|
||||
|
||||
您也可以使用发行版 API 来收集信息，例如人们下载发行版资产的次数。 更多信息请参阅“[发行版](/rest/reference/repos#releases)”。
|
||||
您也可以使用发行版 API 来收集信息，例如人们下载发行版资产的次数。 更多信息请参阅“[发行版](/rest/reference/releases)”。
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## 存储和带宽配额
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
date: '2021-11-09'
|
||||
sections:
|
||||
security_fixes:
|
||||
- A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870.
|
||||
- 包已更新到最新的安全版本。
|
||||
- Packages have been updated to the latest security versions.
|
||||
bugs:
|
||||
- Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration.
|
||||
- Unicorn worker counts might have been set incorrectly in clustering mode.
|
||||
@@ -15,10 +14,10 @@ sections:
|
||||
- Hookshot Go sent distribution type metrics that Collectd could not handle, which caused a ballooning of parsing errors.
|
||||
- Public repositories displayed unexpected results from {% data variables.product.prodname_secret_scanning %} with a type of `Unknown Token`.
|
||||
known_issues:
|
||||
- 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。
|
||||
- 自定义防火墙规则在升级过程中被删除。
|
||||
- Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
|
||||
- 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
|
||||
- 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
|
||||
- 当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。
|
||||
- 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。
|
||||
- On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user.
|
||||
- Custom firewall rules are removed during the upgrade process.
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
|
||||
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
|
||||
- When a replica node is offline in a high availability configuration, {% data variables.product.product_name %} may still route {% data variables.product.prodname_pages %} requests to the offline node, reducing the availability of {% data variables.product.prodname_pages %} for users.
|
||||
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
date: '2021-11-09'
|
||||
sections:
|
||||
security_fixes:
|
||||
- A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870.
|
||||
- 包已更新到最新的安全版本。
|
||||
- Packages have been updated to the latest security versions.
|
||||
bugs:
|
||||
- Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration.
|
||||
- Unicorn worker counts might have been set incorrectly in clustering mode.
|
||||
@@ -12,7 +11,7 @@ sections:
|
||||
- Upgrading from {% data variables.product.prodname_ghe_server %} 2.x to 3.x failed when there were UTF8 characters in an LDAP configuration.
|
||||
- Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations.
|
||||
- The documentation link for Server Statistics was broken.
|
||||
- 'When a new tag was created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload did not display a correct `head_commit` object. Now, when a new tag is created, the push webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload''s `after` commit.'
|
||||
- When a new tag was created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload did not display a correct `head_commit` object. Now, when a new tag is created, the push webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload's `after` commit.
|
||||
- The enterprise audit log page would not display audit events for {% data variables.product.prodname_secret_scanning %}.
|
||||
- There was an insufficient job timeout for replica repairs.
|
||||
- A repository's releases page would return a 500 error when viewing releases.
|
||||
@@ -22,10 +21,10 @@ sections:
|
||||
changes:
|
||||
- Kafka configuration improvements have been added. When deleting repositories, package files are now immediately deleted from storage account to free up space. `DestroyDeletedPackageVersionsJob` now deletes package files from storage account for stale packages along with metadata records.
|
||||
known_issues:
|
||||
- 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。
|
||||
- 自定义防火墙规则在升级过程中被删除。
|
||||
- Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
|
||||
- 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
|
||||
- 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
|
||||
- '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
|
||||
- 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。
|
||||
- On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user.
|
||||
- Custom firewall rules are removed during the upgrade process.
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
|
||||
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
|
||||
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
|
||||
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
|
||||
|
||||
@@ -5,52 +5,52 @@ deprecated: true
|
||||
intro: |
|
||||
{% note %}
|
||||
|
||||
**Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
|
||||
**注意：** 如果 {% data variables.product.product_location %} 正在运行候选发行版，则无法使用热补丁进行升级。我们建议仅在测试环境中运行候选版本。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
|
||||
有关升级说明，请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)”。
|
||||
sections:
|
||||
features:
|
||||
-
|
||||
heading: Security Manager role
|
||||
heading: 安全管理员角色
|
||||
notes:
|
||||
- |
|
||||
Organization owners can now grant teams the access to manage security alerts and settings on their repositories. The "security manager" role can be applied to any team and grants the team's members the following access:
|
||||
组织所有者现在可以授予团队管理其存储库上的安全警报和设置的权限。“安全管理员”角色可以应用于任何团队，并向团队成员授予以下访问权限：
|
||||
|
||||
- Read access on all repositories in the organization.
|
||||
- Write access on all security alerts in the organization.
|
||||
- Access to the organization-level security tab.
|
||||
- Write access on security settings at the organization level.
|
||||
- Write access on security settings at the repository level.
|
||||
- 对组织中所有存储库的读取访问权限。
|
||||
- 对组织中所有安全警报的写入访问权限。
|
||||
- 对组织级别安全选项卡的访问权限。
|
||||
- 对组织级别安全设置的写入访问权限。
|
||||
- 对存储库级别安全设置的写入访问权限。
|
||||
|
||||
For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)."
|
||||
更多信息请参阅“[管理组织中的安全管理员](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)”。
|
||||
-
|
||||
heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling'
|
||||
heading: '用于 GitHub Actions 的临时自托管运行器和用于自动缩放的新 web 挂钩'
|
||||
notes:
|
||||
- |
|
||||
{% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier.
|
||||
{% data variables.product.prodname_actions %} 现在支持临时（单个作业）自托管运行器和新的 ['workflow_job'](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) web 挂钩，使自动缩放运行器更容易。
|
||||
|
||||
Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.product.product_location %}, allowing you to perform any post-job management.
|
||||
临时运行器适用于需要每个作业在干净映像上运行的自我管理环境。运行作业后，临时运行器会自动从 {% data variables.product.product_location %} 中取消注册，从而允许您执行任何作业后管理。
|
||||
|
||||
You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests.
|
||||
您可以将临时运行器与新的 `workflow_job` web 挂钩组合在一起，以自动缩放自托管运行器来响应 {% data variables.product.prodname_actions %} 作业请求。
|
||||
|
||||
For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)."
|
||||
更多信息请参阅“[使用自托管运行器自动缩放](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)”和“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)”。
|
||||
-
|
||||
heading: 'Dark high contrast theme'
|
||||
heading: '深色高对比度主题'
|
||||
notes:
|
||||
- |
|
||||
A dark high contrast theme, with greater contrast between foreground and background elements, is now available on {% data variables.product.prodname_ghe_server %} 3.3. This release also includes improvements to the color system across all {% data variables.product.company_short %} themes.
|
||||
深色高对比度主题的前景和背景元素之间对比度更高，现在 {% data variables.product.prodname_ghe_server %} 3.3 上可用。此版本还包括对所有 {% data variables.product.company_short %} 主题的颜色系统的改进。
|
||||
|
||||
|
||||
！[在外观设置页面上在深色默认主题和深色高对比度之间切换的动画图像](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif)
|
||||
|
||||
For more information about changing your theme, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
|
||||
有关更改主题的更多信息，请参阅“[管理主题设置](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)”。
|
||||
changes:
|
||||
-
|
||||
heading: 管理更改
|
||||
notes:
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.'
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."'
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.3 包括对存储库维护的改进，特别是对于包含许多无法访问的对象的存储库。请注意，升级到 {% data variables.product.prodname_ghe_server %} 3.3 后的第一个维护周期可能需要比平时更长的时间才能完成。'
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.3 包括用于地理位置分散团队和 CI 基础结构的存储库缓存的公共测试版。存储库缓存将存储库的只读副本保存在其他地理位置，从而防止客户端从主实例下载重复的 Git 内容。更多信息请参阅“[关于存储库缓存](/admin/enterprise-management/caching-repositories/about-repository-caching)”。'
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."'
|
||||
- A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity.
|
||||
-
|
||||
|
||||
@@ -4,44 +4,44 @@ intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodn
|
||||
sections:
|
||||
features:
|
||||
-
|
||||
heading: Security Manager role
|
||||
heading: 安全管理员角色
|
||||
notes:
|
||||
- |
|
||||
Organization owners can now grant teams the access to manage security alerts and settings on their repositories. The "security manager" role can be applied to any team and grants the team's members the following access:
|
||||
组织所有者现在可以授予团队管理其存储库上的安全警报和设置的权限。“安全管理员”角色可以应用于任何团队，并向团队成员授予以下访问权限：
|
||||
|
||||
- Read access on all repositories in the organization.
|
||||
- Write access on all security alerts in the organization.
|
||||
- Access to the organization-level security tab.
|
||||
- Write access on security settings at the organization level.
|
||||
- Write access on security settings at the repository level.
|
||||
- 对组织中所有存储库的读取访问权限。
|
||||
- 对组织中所有安全警报的写入访问权限。
|
||||
- 对组织级别安全选项卡的访问权限。
|
||||
- 对组织级别安全设置的写入访问权限。
|
||||
- 对存储库级别安全设置的写入访问权限。
|
||||
|
||||
For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)."
|
||||
更多信息请参阅“[管理组织中的安全管理员](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)”。
|
||||
-
|
||||
heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling'
|
||||
heading: '用于 GitHub Actions 的临时自托管运行器和用于自动缩放的新 web 挂钩'
|
||||
notes:
|
||||
- |
|
||||
{% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier.
|
||||
{% data variables.product.prodname_actions %} 现在支持临时（单个作业）自托管运行器和新的 ['workflow_job'](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) web 挂钩，使自动缩放运行器更容易。
|
||||
|
||||
Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.product.product_location %}, allowing you to perform any post-job management.
|
||||
临时运行器适用于需要每个作业在干净映像上运行的自我管理环境。运行作业后，临时运行器会自动从 {% data variables.product.product_location %} 中取消注册，从而允许您执行任何作业后管理。
|
||||
|
||||
You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests.
|
||||
您可以将临时运行器与新的 `workflow_job` web 挂钩组合在一起，以自动缩放自托管运行器来响应 {% data variables.product.prodname_actions %} 作业请求。
|
||||
|
||||
For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)."
|
||||
更多信息请参阅“[使用自托管运行器自动缩放](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)”和“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)”。
|
||||
-
|
||||
heading: 'Dark high contrast theme'
|
||||
heading: '深色高对比度主题'
|
||||
notes:
|
||||
- |
|
||||
A dark high contrast theme, with greater contrast between foreground and background elements, is now available on {% data variables.product.prodname_ghe_server %} 3.3. This release also includes improvements to the color system across all {% data variables.product.company_short %} themes.
|
||||
深色高对比度主题的前景和背景元素之间对比度更高，现在 {% data variables.product.prodname_ghe_server %} 3.3 上可用。此版本还包括对所有 {% data variables.product.company_short %} 主题的颜色系统的改进。
|
||||
|
||||
|
||||
！[在外观设置页面上在深色默认主题和深色高对比度之间切换的动画图像](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif)
|
||||
|
||||
For more information about changing your theme, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
|
||||
有关更改主题的更多信息，请参阅“[管理主题设置](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)”。
|
||||
changes:
|
||||
-
|
||||
heading: 管理更改
|
||||
notes:
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.'
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."'
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.3 包括对存储库维护的改进，特别是对于包含许多无法访问的对象的存储库。请注意，升级到 {% data variables.product.prodname_ghe_server %} 3.3 后的第一个维护周期可能需要比平时更长的时间才能完成。'
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.3 包括用于地理位置分散团队和 CI 基础结构的存储库缓存的公共测试版。存储库缓存将存储库的只读副本保存在其他地理位置，从而防止客户端从主实例下载重复的 Git 内容。更多信息请参阅“[关于存储库缓存](/admin/enterprise-management/caching-repositories/about-repository-caching)”。'
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."'
|
||||
- A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity.
|
||||
- The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09]
|
||||
|
||||
@@ -5,11 +5,11 @@ deprecated: false
|
||||
intro: |
|
||||
{% note %}
|
||||
|
||||
**Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
|
||||
**注意：** 如果 {% data variables.product.product_location %} 正在运行候选发行版，则无法使用热补丁进行升级。我们建议仅在测试环境中运行候选版本。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
|
||||
有关升级说明，请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)”。
|
||||
sections:
|
||||
features:
|
||||
-
|
||||
|
||||
@@ -1 +1 @@
|
||||
The branch or tag name that triggered the workflow run.
|
||||
触发工作流程的分支或标记名称。
|
||||
|
||||
@@ -1 +1 @@
|
||||
`true` if branch protections are configured for the ref that triggered the workflow run.
|
||||
如果为触发工作流运行的 ref 配置了分支保护，则为 `true`。
|
||||
|
||||
@@ -1 +1 @@
|
||||
The type of ref that triggered the workflow run. Valid values are `branch` or `tag`.
|
||||
触发工作流程运行的引用类型。 有效值为 `branch` 或 `tag`。
|
||||
|
||||
@@ -1 +1 @@
|
||||
To get started with {% data variables.product.prodname_codespaces %}, see "[Quickstart for {% data variables.product.prodname_codespaces %}](/codespaces/getting-started/quickstart)." To learn more about how {% data variables.product.prodname_codespaces %} works, see "[Deep dive into Codespaces](/codespaces/getting-started/deep-dive)."
|
||||
要开始使用 {% data variables.product.prodname_codespaces %}，请参阅“[{% data variables.product.prodname_codespaces %}](/codespaces/getting-started/quickstart)快速入门</0>”。 要了解有关 {% data variables.product.prodname_codespaces %} 工作原理的更多信息，请参阅“[深入了解代码空间](/codespaces/getting-started/deep-dive)”。
|
||||
|
||||
@@ -1 +1 @@
|
||||
{% ifversion not ghec%}By default, a{% else %}A{% endif %} user account is considered to be dormant if it has not been active for 90 days. {% ifversion not ghec %}You can configure the length of time a user must be inactive to be considered dormant{% ifversion ghes%} and choose to suspend dormant users to release user licenses{% endif %}.{% endif %}
|
||||
{% ifversion not ghec%}默认情况下，如果{% else %}{% endif %} 用户帐户在 90 天内未处于活动状态，则该用户帐户被视为处于休眠状态。 {% ifversion not ghec %}您可以配置用户必须处于非活动状态才能被视为休眠{% ifversion ghes%} 的时间长度，并选择挂起休眠用户以释放用户许可证{% endif %}。{% endif %}
|
||||
|
||||
@@ -3,4 +3,4 @@
|
||||
- 评论问题和拉取请求。
|
||||
- 创建、删除、关注仓库和加星标。
|
||||
- 推送提交。
|
||||
- Accessing resources by using a personal access token or SSH key.
|
||||
- 使用个人访问令牌或 SSH 密钥访问资源。
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** The Dormant Users report is currently in beta and subject to change. During the beta, ongoing improvements to the report download feature may limit its availability.
|
||||
**注意：** “休眠用户”报告目前处于测试阶段，可能会有所变化。 在测试期间，对报告下载功能的持续改进可能会限制其可用性。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. In the enterprise account sidebar, click {% octicon "checklist" aria-label="The Compliance icon" %} **Compliance**. 
|
||||
1. 在企业帐户侧边栏中，单击 {% octicon "checklist" aria-label="The Compliance icon" %} **Compliance（合规性）**。 
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
1. 在文件列表上方，单击 {% octicon "download" aria-label="The download icon" %} ****Code（代码）。 
|
||||
1. 要使用 HTTPS 克隆仓库，请在“Clone with HTTPS（使用 HTTPS 克隆）”下单击
|
||||
{% octicon "clippy" aria-label="The clipboard icon" %}. 要使用 SSH 密钥克隆仓库，包括组织的 SSH 认证中心颁发的证书，单击 **Use SSH（使用 SSH）**，然后单击 {% octicon "clippy" aria-label="The clipboard icon" %}。 要使用 {% data variables.product.prodname_cli %} 克隆存储库，请单击 **使用 {% data variables.product.prodname_cli %}**，然后单击 {% octicon "clippy" aria-label="The clipboard icon" %}。
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
{% endif %}
|
||||
1. Copy the URL for the repository.
|
||||
|
||||
- To clone the repository using HTTPS, under "HTTPS", click {% octicon "clippy" aria-label="The clipboard icon" %}.
|
||||
- 要使用 SSH 密钥克隆仓库，包括组织的 SSH 认证中心颁发的证书，单击 **SSH**，然后单击 {% octicon "clippy" aria-label="The clipboard icon" %}。
|
||||
- To clone a repository using {% data variables.product.prodname_cli %}, click **{% data variables.product.prodname_cli %}**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. 
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
- SOC 1, Type 2
|
||||
- SOC 2, Type 2
|
||||
- Cloud Security Alliance CAIQ self-assessment (CSA CAIQ)
|
||||
- ISO/IEC 27001:2013 certification
|
||||
- {% data variables.product.prodname_dotcom_the_website %} Services Continuity and Incident Management Plan
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
**注意：** {% data variables.product.company_short %} 在 2022 年 3 月 15 日通过删除较旧的不安全密钥类型提高了安全性。
|
||||
@@ -7,3 +8,4 @@
|
||||
在 2021 年 11 月 2 日之前 `valid_after` 的 RSA 密钥 (`ssh-rsa`) 可以继续使用任何签名算法。 在该日期之后生成的 RSA 密钥必须使用 SHA-2 签名算法。 某些较旧的客户端可能需要升级才能使用 SHA-2 签名。
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -20,14 +20,14 @@
|
||||
- 选择 **{% data variables.product.support_ticket_priority_low %}** 以提出一般问题和提交有关新功能、购买、培训或状态检查的请求。
|
||||
{%- endif %}
|
||||
{%- ifversion ghes or ghec %}
|
||||
1. Optionally, if your account includes {% data variables.contact.premium_support %} and your ticket is {% ifversion ghes %}urgent or high{% elsif ghec %}high{% endif %} priority, you can request a callback in English. Select **Request a callback from GitHub Support**, select the country code dropdown menu to choose your country, and enter your phone number. 
|
||||
1. （可选）如果您的帐户包含 {% data variables.contact.premium_support %} 并且您的事件单为 {% ifversion ghes %}紧急或高{% elsif ghec %}高{% endif %} 优先级，则可以请求英语回电。 选择 **Request a callback from GitHub Support（请求 GitHub 支持回电）**，选择国家/地区代码下拉菜单以选择您所在的国家/地区，然后输入您的电话号码。 
|
||||
{%- endif %}
|
||||
1. 在“Subject（主题）”下，为您遇到的问题输入描述性标题。 
|
||||
1. 在“How can we help（我们如何提供帮助）”下，提供将帮助支持团队对问题进行故障排除的任何其他信息。 You can use markdown to format your message.  Helpful information may include:
|
||||
1. 在“Subject（主题）”下，为您遇到的问题输入描述性标题。 
|
||||
1. 在“How can we help（我们如何提供帮助）”下，提供将帮助支持团队对问题进行故障排除的任何其他信息。 您可以使用 Markdown 格式化消息。  有用的信息可能包括：
|
||||
- 重现问题的步骤
|
||||
- 与发现问题相关的任何特殊情况（例如，首次发生或特定活动后发生、发生频率、问题的业务影响以及建议的紧迫程度）
|
||||
- 错误消息的准确表述
|
||||
{%- ifversion ghes %}
|
||||
1. Optionally, attach diagnostics files and other files by dragging and dropping, uploading, or pasting from the clipboard.
|
||||
1. （可选）通过拖放、上传或从剪贴板粘贴来附加诊断文件及其他文件。
|
||||
{%- endif %}
|
||||
1. 单击 **Send request（发送请求）**。 
|
||||
1. 单击 **Send request（发送请求）**。 
|
||||
|
||||
Reference in New Issue
Block a user