Skip to content

Commit a0844f6

Browse files
authored
New translation batch for cn (github#25713)
* Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check parsing * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=cn * run script/i18n/reset-known-broken-translation-files.js * Check in cn CSV report
1 parent dde4ae9 commit a0844f6

File tree

20 files changed

+113
-106
lines changed

20 files changed

+113
-106
lines changed

translations/log/cn-resets.csv

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,10 @@ translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgr
8484
translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags
8585
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags
8686
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md,parsing error
87+
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags
8788
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags
89+
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,broken liquid tags
90+
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md,broken liquid tags
8891
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,broken liquid tags
8992
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,broken liquid tags
9093
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,broken liquid tags

translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -75,12 +75,12 @@ shortTitle: 管理您的订阅
7575
- 忽略某仓库的所有通知
7676
{%- endif %}
7777
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5819 %}
78-
1. (可选)要取消订阅指定用户或组织拥有的所有存储库,请选择 **Unwatch all(全部取消关注)**下拉列表,然后单击要取消订阅其存储库的组织。 The button to unwatch all repositories is only available if you are watching all activity or custom notifications on over 10 repositories.
78+
1. (可选)要取消订阅指定用户或组织拥有的所有存储库,请选择 **Unwatch all(全部取消关注)**下拉列表,然后单击要取消订阅其存储库的组织。 取消关注所有存储库的按钮仅在您正在关注超过 10 个存储库上的所有活动或自定义通知时才可用。
7979

80-
![Screenshot of the Unwatch All button.](/assets/images/help/notifications-v2/unsubscribe-from-all-repos.png)
80+
![“全部取消关注”按钮的屏幕截图](/assets/images/help/notifications-v2/unsubscribe-from-all-repos.png)
8181

82-
- Click **Unwatch** to confirm that you want to unwatch the repositories owned by the selected user or organization, or click **Cancel** to cancel.
82+
- 单击 **Unwatch(取消关注)**以确认您要取消关注所选用户或组织拥有的存储库,或单击 **Cancel(取消)**以取消。
8383

84-
![Screenshot of the unwatch all confirmation dialogue.](/assets/images/help/notifications-v2/unwatch-repo-dialog.png)
84+
![全部取消关注确认对话框的屏幕截图。](/assets/images/help/notifications-v2/unwatch-repo-dialog.png)
8585

8686
{% endif %}

translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ topics:
3131
访问您的个人资料的人也可以看到以下信息。
3232

3333
- 你拥有或参与的仓库和 gists。 {% ifversion fpt or ghes or ghec %}您可以通过将仓库和 Gist 固定到个人资料中来展示您的最佳作品。 更多信息请参阅“[将项目嵌入到个人资料](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)”。{% endif %}
34-
- Repositories you've starred{% ifversion fpt or ghec %} and organized into lists.{% endif %} For more information, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)."
34+
- 您已加星标{% ifversion fpt or ghec %} 并组织到列表中的存储库。{% endif %} 更多信息请参阅“[保存有星标的存储库](/articles/saving-repositories-with-stars/)”。
3535
- 您在经常参与的组织、仓库和团队中的活动概述。 更多信息请参阅“[在您的个人资料中显示活动概述](/articles/showing-an-overview-of-your-activity-on-your-profile)”。{% ifversion fpt or ghec %}
3636
- 徽章,显示您是否使用 {% 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 %}
3737

translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ shortTitle: 删除用户帐户
1717

1818
删除用户帐户会移除帐户所拥有的所有仓库、私有仓库分支、wiki、议题、拉取请求和页面。 {% ifversion fpt or ghec %} 在其他用户拥有的仓库中创建的议题和拉取请求以及所做的评论将不会被删除,而是与我们的[Ghost 用户](https://github.com/ghost)关联。{% else %}在其他用户拥有的仓库中创建的议题和拉取请求以及所做的评论将不会被删除。{% endif %}
1919

20-
{% ifversion fpt or ghec %} When you delete your account we stop billing you. The email address associated with the account becomes available for use with a different account on {% data variables.product.product_location %}. After 90 days, the account name also becomes available to anyone else to use on a new account. {% endif %}
20+
{% ifversion fpt or ghec %} 当您删除帐户时,我们会停止对您计费。 与该帐户关联的电子邮件地址可用于 {% data variables.product.product_location %} 上不同的帐户。 90 天后,该帐户名称也可供其他任何人用于新帐户。 {% endif %}
2121

2222
如果您是组织的唯一所有者,则必须先将所有权转让给其他人或删除该组织,然后才能删除您的用户帐户。 如果组织中有其他所有者,则必须先从组织中删除自己,然后才能删除用户帐户。
2323

@@ -44,7 +44,7 @@ shortTitle: 删除用户帐户
4444
- 如果您是组织中的唯一所有者,则必须将所有权转让给其他人或删除您的组织。
4545
- 如果组织中有其他组织所有者,则必须将自己从组织中删除。 ![帐户删除按钮](/assets/images/help/settings/settings-account-delete.png)
4646
4. 在“Make sure you want to do this(确保要执行此操作)”对话框中,完成以下步骤,以确认您了解删除帐户时会发生什么: ![删除帐户确认对话框](/assets/images/help/settings/settings-account-deleteconfirm.png)
47-
{% ifversion fpt or ghec %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and {% data variables.product.prodname_pages %} sites owned by your account will be deleted and your billing will end immediately, and your username will be available to anyone for use on {% data variables.product.product_name %} after 90 days.
47+
{% ifversion fpt or ghec %}- 请记住,您的帐户拥有的所有存储库、私有存储库的分支、wiki、议题、拉取请求和 {% data variables.product.prodname_pages %} 网站都将被删除,您的计费将立即结束,并且您的用户名在 90 天后可供任何人在 {% data variables.product.product_name %} 上使用。
4848
{% else %}- 重新考虑一下,您帐户拥有的所有仓库、私有仓库分支、wiki、议题、提取请求和网页都将被删除,并且任何人将可在 {% data variables.product.product_name %} 上使用您的用户名。
4949
{% endif %}- 在第一个字段中,输入您的 {% data variables.product.product_name %} 用户名或电子邮件。
5050
- 在第二个字段中,键入提示短语。

translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -265,13 +265,13 @@ The attacker server can use the {% ifversion fpt or ghec %}{% data variables.pro
265265

266266
## 自托管运行器的强化
267267

268-
{% ifversion fpt %}
268+
{% ifversion fpt or ghec %}
269269
**{% data variables.product.prodname_dotcom %} 托管的**运行程序在临时和干净的隔离虚拟机中执行代码,这意味着无法持续破坏此环境,可以访问的信息不会超过引导过程中此环境中存在的信息。
270270
{% endif %}
271271

272-
{% ifversion fpt %}**Self-hosted**{% elsif ghes or ghae %}Self-hosted{% endif %} runners for {% data variables.product.product_name %} do not have guarantees around running in ephemeral clean virtual machines, and can be persistently compromised by untrusted code in a workflow.
272+
{% ifversion fpt or ghec %}**Self-hosted**{% elsif ghes or ghae %}Self-hosted{% endif %} runners for {% data variables.product.product_name %} do not have guarantees around running in ephemeral clean virtual machines, and can be persistently compromised by untrusted code in a workflow.
273273

274-
{% ifversion fpt %}As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal repositories, as anyone who can fork the repository and open a pull request (generally those with read-access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, depending on its settings, can grant {% else %} grants {% endif %}write-access permissions on the repository. 尽管工作流程可以通过使用环境和必需的审查来控制对环境密钥的访问,但是这些工作流程不是在隔离的环境中运行,在自托管运行程器上运行时仍然容易遭受相同的风险。
274+
{% ifversion fpt or ghec %}As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal repositories, as anyone who can fork the repository and open a pull request (generally those with read-access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, depending on its settings, can grant {% else %} grants {% endif %}write-access permissions on the repository. 尽管工作流程可以通过使用环境和必需的审查来控制对环境密钥的访问,但是这些工作流程不是在隔离的环境中运行,在自托管运行程器上运行时仍然容易遭受相同的风险。
275275

276276
在组织或企业级别定义自托管运行器时, {% data variables.product.product_name %} 可将多个仓库中的工作流程安排到同一个运行器中。 因此,这些环境的安全危害可能会导致广泛的影响。 为了帮助缩小损害范围,可以通过将自托管运行器组织到单独的组中来创建边界。 更多信息请参阅“[使用组管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)”。
277277

Lines changed: 24 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: 关于代码空间的计费
33
shortTitle: 关于计费
4-
intro: 'View pricing and see how to manage {% data variables.product.prodname_codespaces %} billing for your organization.'
4+
intro: '查看定价并了解如何管理组织的 {% data variables.product.prodname_codespaces %} 计费。'
55
permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.'
66
versions:
77
fpt: '*'
@@ -13,20 +13,20 @@ topics:
1313
- Billing
1414
---
1515

16-
## {% data variables.product.prodname_codespaces %} pricing
16+
## {% data variables.product.prodname_codespaces %} 定价
1717

18-
{% data variables.product.prodname_codespaces %} usage is billed for all accounts on the Team and Enterprise plans, and does not include any entitlements. Individual accounts are not currently billed for {% data variables.product.prodname_codespaces %} usage.
18+
{% data variables.product.prodname_codespaces %} 的使用将针对团队和企业计划中的所有帐户计费,并且不包括任何权利。 个人帐户目前不为 {% data variables.product.prodname_codespaces %} 使用付费。
1919

20-
{% data variables.product.prodname_codespaces %} usage is billed according to the units of measure in the following table:
20+
{% data variables.product.prodname_codespaces %} 使用按下表中的计量单位计费:
2121

22-
| 产品 | SKU | Unit of measure | Price |
23-
| ------------------ | ------ | --------------- | ----- |
24-
| Codespaces Compute | 2 个内核 | 1 hour | $0.18 |
25-
| | 4 个内核 | 1 hour | $0.36 |
26-
| | 8 个内核 | 1 hour | $0.72 |
27-
| | 16 个内核 | 1 hour | $1.44 |
28-
| | 32 个内核 | 1 hour | $2.88 |
29-
| Codespaces Storage | 存储器 | 1 GB-month | $0.07 |
22+
| 产品 | SKU | 计量单位 | 价格 |
23+
| ------------- | ------ | ------ | ----- |
24+
| Codespaces 计算 | 2 个内核 | 1 小时 | $0.18 |
25+
| | 4 个内核 | 1 小时 | $0.36 |
26+
| | 8 个内核 | 1 小时 | $0.72 |
27+
| | 16 个内核 | 1 小时 | $1.44 |
28+
| | 32 个内核 | 1 小时 | $2.88 |
29+
| Codespaces 存储 | 存储器 | 1 GB- | $0.07 |
3030

3131
## 关于 {% data variables.product.prodname_codespaces %} 的计费
3232

@@ -40,36 +40,36 @@ If you purchased {% data variables.product.prodname_enterprise %} through a Micr
4040

4141
{% data reusables.dotcom_billing.pricing_cal %}
4242

43-
### Billing for {% data variables.product.prodname_codespaces %} prebuilds
43+
### {% data variables.product.prodname_codespaces %} 预构建的计费
4444

4545
{% data reusables.codespaces.prebuilds-beta-note %}
4646

4747
{% data reusables.codespaces.billing-for-prebuilds %}
4848

49-
## Setting a spending limit
49+
## 设置支出限制
5050

5151
{% data reusables.codespaces.codespaces-spending-limit-requirement %}
5252

5353
有关管理和更改帐户支出限制的信息,请参阅“[管理 {% data variables.product.prodname_codespaces %} 的支出限制](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)”。
5454

5555
{% data reusables.codespaces.exporting-changes %}
5656

57-
## Limiting the choice of machine types
57+
## 限制机器类型的选择
5858

59-
The type of machine a user chooses when they create a codespace affects the per-minute charge for that codespace, as shown above.
59+
用户在创建代码空间时选择的计算机类型会影响该代码空间的每分钟费用,如上所示。
6060

61-
Organization owners can create a policy to restrict the machine types that are available to users. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
61+
组织所有者可以创建策略来限制用户可用的计算机类型。 For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
6262

63-
## How billing is handled for forked repositories
63+
## 如何处理复刻的存储库的计费
6464

65-
{% data variables.product.prodname_codespaces %} can only be used in organizations where a billable owner has been defined. To incur charges to the organization, the user must be a member or collaborator, otherwise they cannot create a codespace.
65+
{% data variables.product.prodname_codespaces %} 只能在定义了计费所有者的组织中使用。 要对组织收费,用户必须是成员或协作者,否则他们无法创建代码空间。
6666

67-
For example, a user in a private organization can fork a repository within that organization, and can subsequently use a codespace billed to the organization; this is because the organization is the owner of the parent repository, which can remove the user's access, the forked repository, and the codespace.
67+
例如,私有组织中的用户可以复刻该组织内的存储库,随后可以使用向组织计费的代码空间;这是因为组织是父存储库的所有者,父存储库可以删除用户的访问权限、复刻的存储库和代码空间。
6868

69-
## How billing is handled when a repository is transferred
69+
## 传输存储库时如何处理计费
7070

71-
Usage is billed and reported on every hour. As such, you pay for any usage when a repository is within your organization. When a repository is transferred out of your organization, any codespaces in that repository are removed as part of the transfer process.
71+
使用每小时计费和报告。 因此,当存储库位于您的组织内时,您需要为任何使用付费。 将存储库移出组织时,该存储库中的所有代码空间都将作为传输过程的一部分被删除。
7272

73-
## What happens when users are removed
73+
## 移除用户后会发生什么情况
7474

75-
If a user is removed from an organization or repository, their codespaces are automatically deleted.
75+
如果从组织或存储库中移除用户,则会自动删除其代码空间。

translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Managing your license for GitHub Enterprise
3-
shortTitle: GitHub Enterprise license
4-
intro: '{% data variables.product.prodname_enterprise %} includes both cloud and self-hosted deployment options. If you host a {% data variables.product.prodname_ghe_server %} instance, you must unlock the instance with a license file. You can view, manage, and update the license file.'
2+
title: 管理 GitHub Enterprise 的许可证
3+
shortTitle: GitHub Enterprise 许可证
4+
intro: '{% data variables.product.prodname_enterprise %} 包括云和自托管部署选项。 如果您托管 {% data variables.product.prodname_ghe_server %} 实例,则必须使用许可文件解锁该实例。 您可以查看、管理和更新许可证文件。'
55
redirect_from:
66
- /free-pro-team@latest/billing/managing-your-license-for-github-enterprise
77
- /enterprise/admin/installation/managing-your-github-enterprise-license

0 commit comments

Comments
 (0)