зеркало из https://github.com/github/docs.git
New translation batch for cn (#29918)
* 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
Родитель
061806add1
Коммит
b6e36f5d65
|
|
@ -385,7 +385,7 @@ translations/zh-CN/data/reusables/enterprise_installation/hardware-consideration
|
|||
translations/zh-CN/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,rendering error
|
||||
translations/zh-CN/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md,rendering error
|
||||
translations/zh-CN/data/reusables/gated-features/packages.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/gated-features/secret-scanning-partner.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/gated-features/secret-scanning.md,broken liquid tags
|
||||
|
|
@ -406,9 +406,9 @@ translations/zh-CN/data/reusables/package_registry/packages-cluster-support.md,b
|
|||
translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/repositories/enable-security-alerts.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/repositories/select-marketplace-apps.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/saml/saml-session-oauth.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/saml/saml-session-oauth.md,rendering error
|
||||
translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,Listed in localization-support#489
|
||||
translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,rendering error
|
||||
translations/zh-CN/data/reusables/scim/after-you-configure-saml.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/secret-scanning/partner-program-link.md,broken liquid tags
|
||||
|
|
|
|||
|
|
|
@ -25,7 +25,7 @@ versions:
|
|||
|
||||
操作可以与运行器机器进行通信，以设置环境变量，其他操作使用的输出值，将调试消息添加到输出日志和其他任务。
|
||||
|
||||
大多数工作流程命令使用特定格式的 `echo` 命令，而其他工作流程则通过写入文件被调用。 更多信息请参阅“[环境文件](#environment-files)”。
|
||||
大多数工作流程命令使用特定格式的 `echo` 命令，而其他工作流程则通过写入文件被调用。 For more information, see "[Environment files](#environment-files)."
|
||||
|
||||
### 示例
|
||||
|
||||
|
|
@ -623,6 +623,12 @@ steps:
|
|||
{delimiter}
|
||||
```
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Make sure the delimiter you're using is randomly generated and unique for each run. For more information, see "[Understanding the risk of script injections](/actions/security-guides/security-hardening-for-github-actions#understanding-the-risk-of-script-injections)".
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
#### 示例
|
||||
|
||||
此示例使用 `EOF` 作为分隔符，并将 `JSON_RESPONSE` 环境变量设置为 `curl` 响应的值。
|
||||
|
|
|
|||
|
|
@ -96,7 +96,7 @@ shortTitle: 仓库管理策略
|
|||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
{% data reusables.enterprise-accounts.repositories-tab %}
|
||||
5. 在“Repository creation”下，检查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
|
||||
{% ifversion ghes or ghae %}
|
||||
{% ifversion ghes or ghae or ghec %}
|
||||
{% data reusables.enterprise-accounts.repo-creation-policy %}
|
||||
{% data reusables.enterprise-accounts.repo-creation-types %}
|
||||
{% else %}
|
||||
|
|
|
|||
|
|
@ -51,10 +51,10 @@ To use {% data variables.product.prodname_actions %} to upload a third-party SAR
|
|||
|
||||
Your workflow will need to use the `upload-sarif` action, which is part of the `github/codeql-action` repository. It has input parameters that you can use to configure the upload. The main input parameters you'll use are:
|
||||
|
||||
- `sarif-file`, which configures the file or directory of SARIF files to be uploaded. The directory or file path is relative to the root of the repository.
|
||||
- `sarif-file`, which configures the file or directory of SARIF files to be uploaded. The directory or file path is relative to the root of the repository.
|
||||
- `category` (optional), which assigns a category for results in the SARIF file. This enables you to analyze the same commit in multiple ways and review the results using the {% data variables.product.prodname_code_scanning %} views in {% data variables.product.prodname_dotcom %}. For example, you can analyze using multiple tools, and in mono-repos, you can analyze different slices of the repository based on the subset of changed files.
|
||||
|
||||
For more information see the [`upload-sarif` action](https://github.com/github/codeql-action/tree/v1/upload-sarif).
|
||||
For more information see the [`upload-sarif` action](https://github.com/github/codeql-action/tree/{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}/upload-sarif).
|
||||
|
||||
The `upload-sarif` action can be configured to run when the `push` and `scheduled` event occur. For more information about {% data variables.product.prodname_actions %} events, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
|
||||
|
||||
|
|
@ -66,7 +66,7 @@ If your SARIF file doesn't include `partialFingerprints`, the `upload-sarif` act
|
|||
|
||||
You can create a new workflow that uploads SARIF files after you commit them to your repository. This is useful when the SARIF file is generated as an artifact outside of your repository.
|
||||
|
||||
This example workflow runs anytime commits are pushed to the repository. The action uses the `partialFingerprints` property to determine if changes have occurred. In addition to running when commits are pushed, the workflow is scheduled to run once per week. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
|
||||
This example workflow runs anytime commits are pushed to the repository. The action uses the `partialFingerprints` property to determine if changes have occurred. In addition to running when commits are pushed, the workflow is scheduled to run once per week. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
|
||||
|
||||
This workflow uploads the `results.sarif` file located in the root of the repository. For more information about creating a workflow file, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
|
||||
|
||||
|
|
@ -109,7 +109,7 @@ jobs:
|
|||
|
||||
If you generate your third-party SARIF file as part of a continuous integration (CI) workflow, you can add the `upload-sarif` action as a step after running your CI tests. If you don't already have a CI workflow, you can create one using a {% data variables.product.prodname_actions %} template. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
|
||||
|
||||
This example workflow runs anytime commits are pushed to the repository. The action uses the `partialFingerprints` property to determine if changes have occurred. In addition to running when commits are pushed, the workflow is scheduled to run once per week. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
|
||||
This example workflow runs anytime commits are pushed to the repository. The action uses the `partialFingerprints` property to determine if changes have occurred. In addition to running when commits are pushed, the workflow is scheduled to run once per week. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
|
||||
|
||||
The workflow shows an example of running the ESLint static analysis tool as a step in a workflow. The `Run ESLint` step runs the ESLint tool and outputs the `results.sarif` file. The workflow then uploads the `results.sarif` file to {% data variables.product.prodname_dotcom %} using the `upload-sarif` action. For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
|
||||
|
||||
|
|
|
|||
|
|
@ -67,9 +67,10 @@ topics:
|
|||
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
{% data reusables.repositories.navigate-to-ghas-settings %}
|
||||
{% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
|
||||
{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}{% ifversion secret-scanning-custom-enterprise-35 %}
|
||||
{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}{% ifversion secret-scanning-custom-enterprise-35 or custom-pattern-dry-run-ga %}
|
||||
1. 当您准备好测试新的自定义模式时，要识别存储库中的匹配项而不创建警报，请单击 **Save and dry run（保存并空运行）**。
|
||||
{% data reusables.advanced-security.secret-scanning-dry-run-results %}
|
||||
{%- ifversion secret-scanning-custom-enterprise-35 %}{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}{% endif %}
|
||||
{% endif %}
|
||||
{% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
|
||||
|
||||
|
|
@ -122,10 +123,11 @@ aAAAe9
|
|||
{% data reusables.repositories.navigate-to-ghas-settings %}
|
||||
{% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
|
||||
{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
|
||||
{%- ifversion secret-scanning-custom-enterprise-35 %}
|
||||
{%- ifversion secret-scanning-custom-enterprise-35 or custom-pattern-dry-run-ga %}
|
||||
1. 当您准备好测试新的自定义模式时，要识别所选存储库中的匹配项而不创建警报，请单击 **Save and dry run（保存并试运行）**。
|
||||
{% data reusables.advanced-security.secret-scanning-dry-run-select-repos %}
|
||||
{% data reusables.advanced-security.secret-scanning-dry-run-results %}
|
||||
{%- ifversion secret-scanning-custom-enterprise-35 %}{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}{% endif %}
|
||||
{%- endif %}
|
||||
{% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
|
||||
|
||||
|
|
@ -141,7 +143,7 @@ aAAAe9
|
|||
|
||||
{% note %}
|
||||
|
||||
{% ifversion secret-scanning-custom-enterprise-36 %}
|
||||
{% ifversion secret-scanning-custom-enterprise-36 or custom-pattern-dry-run-ga %}
|
||||
**注意：**
|
||||
- 在企业级别，只有自定义模式的创建者才能编辑该模式，并在试运行中使用它。
|
||||
- 企业所有者只能使用他们有权访问的存储库上的试运行，而企业所有者不一定有权访问企业内的所有组织或存储库。
|
||||
|
|
@ -158,10 +160,11 @@ aAAAe9
|
|||
{% data reusables.enterprise-accounts.advanced-security-security-features %}
|
||||
1. 在“Secret scanning custom patterns（机密扫描自定义模式）”下，单击 {% ifversion ghes = 3.2 %}**New custom pattern（新建自定义模式）**{% else %}**New pattern（新建模式）**{% endif %}。
|
||||
{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
|
||||
{%- ifversion secret-scanning-custom-enterprise-36 %}
|
||||
{%- ifversion secret-scanning-custom-enterprise-36 or custom-pattern-dry-run-ga %}
|
||||
1. 当您准备好测试新的自定义模式时，要识别企业中的匹配项而不创建警报，请单击 **Save and dry run（保存并空运行）**。
|
||||
{% data reusables.advanced-security.secret-scanning-dry-run-select-repos %}
|
||||
{% data reusables.advanced-security.secret-scanning-dry-run-select-enterprise-repos %}
|
||||
{% data reusables.advanced-security.secret-scanning-dry-run-results %}
|
||||
{%- ifversion secret-scanning-custom-enterprise-36 %}{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}{% endif %}
|
||||
{%- endif %}
|
||||
{% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
|
||||
|
||||
|
|
@ -175,7 +178,7 @@ aAAAe9
|
|||
* 对于存储库或组织，显示创建自定义模式的存储库或组织的“安全和分析”设置。 更多信息请参阅“[定义仓库的自定义模式](#defining-a-custom-pattern-for-a-repository)”或“[定义组织的自定义模式](#defining-a-custom-pattern-for-an-organization)”。
|
||||
* 对于企业，在“Policies（策略）”下显示“Advanced Security（高级安全性）”区域，然后单击 **Security features（安全功能）**。 更多信息请参阅上面的“[为企业帐户定义自定义模式](#defining-a-custom-pattern-for-an-enterprise-account)”。
|
||||
2. 在“{% data variables.product.prodname_secret_scanning_caps %}”下要编辑的自定义模式的右侧，单击 {% octicon "pencil" aria-label="The edit icon" %}。
|
||||
{%- ifversion secret-scanning-custom-enterprise-36 %}
|
||||
{%- ifversion secret-scanning-custom-enterprise-36 or custom-pattern-dry-run-ga %}
|
||||
3. 当您准备好测试编辑的自定义模式时，要识别匹配项而不创建警报，请单击 **Save and dry run（保存并空运行）**。
|
||||
{%- endif %}
|
||||
4. 查看并测试更改后，单击 **Save changes（保存更改）**。
|
||||
|
|
|
|||
|
|
@ -18,11 +18,26 @@ topics:
|
|||
|
||||
## 连接到专用网络上的资源
|
||||
|
||||
当前支持的访问专用网络上资源的方法是使用 VPN。 目前不建议允许列表代码空间 IP，因为这将允许所有代码空间（包括您和其他客户的代码空间）访问受保护的网络资源。
|
||||
There are currently two methods of accessing resources on a private network within Codespaces.
|
||||
- Using a {% data variables.product.prodname_cli %} extension to configure your local machine as a gateway to remote resources.
|
||||
- Using a VPN.
|
||||
|
||||
### Using the GitHub CLI extension to access remote resources
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The {% data variables.product.prodname_cli %} extension is currently in beta and subject to change.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
The {% data variables.product.prodname_cli %} extension allows you to create a bridge between a codespace and your local machine, so that the codespace can access any remote resource that is accessible from your machine. The codespace uses your local machine as a network gateway to reach those resources. For more information, see "[Using {% data variables.product.prodname_cli %} to access remote resources](https://github.com/github/gh-net#codespaces-network-bridge)."
|
||||
|
||||
|
||||
|
||||
|
||||
### 使用 VPN 访问专用网络后面的资源
|
||||
|
||||
要访问专用网络后面的资源，最简单方法是从代码空间内通过 VPN 进入该网络。
|
||||
As an alternative to the {% data variables.product.prodname_cli %} extension, you can use a VPN to access resources behind a private network from within your codespace.
|
||||
|
||||
我们建议使用 [OpenVPN](https://openvpn.net/) 等 VPN工具访问专用网络上的资源。 更多信息请参阅“[从 GitHub Codespaces 使用 OpenVPN 客户端](https://github.com/codespaces-contrib/codespaces-openvpn)”。
|
||||
|
||||
|
|
|
|||
|
|
@ -30,6 +30,7 @@ You can work with {% data variables.product.prodname_codespaces %} in the {% da
|
|||
- [Copy a file to/from a codespace](#copy-a-file-tofrom-a-codespace)
|
||||
- [Modify ports in a codespace](#modify-ports-in-a-codespace)
|
||||
- [Access codespace logs](#access-codespace-logs)
|
||||
- [Access remote resources](#access-remote-resources)
|
||||
|
||||
## Installing {% data variables.product.prodname_cli %}
|
||||
|
||||
|
|
@ -197,3 +198,12 @@ gh codespace logs -c <em>codespace-name</em>
|
|||
```
|
||||
|
||||
For more information about the creation log, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs#creation-logs)."
|
||||
|
||||
### Access remote resources
|
||||
You can use the {% data variables.product.prodname_cli %} extension to create a bridge between a codespace and your local machine, so that the codespace can access any remote resource that is accessible from your machine. For more information on using the extension, see "[Using {% data variables.product.prodname_cli %} to access remote resources](https://github.com/github/gh-net#codespaces-network-bridge)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The {% data variables.product.prodname_cli %} extension is currently in beta and subject to change.
|
||||
|
||||
{% endnote %}
|
||||
|
|
@ -22,6 +22,14 @@ When prebuilds are available for a particular branch of a repository, a particul
|
|||
|
||||
|
||||
|
||||
## The prebuild process
|
||||
|
||||
To create a prebuild you set up a prebuild configuration. When you save the configuration, a {% data variables.product.prodname_actions %} workflow runs to create each of the required prebuilds; one workflow per prebuild. Workflows also run whenever the prebuilds for your configuration need to be updated. This can happen at scheduled intervals, on pushes to a prebuild-enabled repository, or when you change the dev container configuration. 更多信息请参阅“[配置预构建](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)”。
|
||||
|
||||
When a prebuild configuration workflow runs, {% data variables.product.prodname_dotcom %} creates a temporary codespace, performing setup operations up to and including any `onCreateCommand` and `updateContentCommand` commands in the `devcontainer.json` file. No `postCreateCommand` commands are run during the creation of a prebuild. For more information about these commands, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. A snapshot of the generated container is then taken and stored.
|
||||
|
||||
When you create a codespace from a prebuild, {% data variables.product.prodname_dotcom %} downloads the existing container snapshot from storage and deploys it on a fresh virtual machine, completing the remaining commands specified in the dev container configuration. Since many operations have already been performed, such as cloning the repository, creating a codespace from a prebuild can be substantially quicker than creating one without a prebuild. This is true where the repository is large and/or `onCreateCommand` commands take a long time to run.
|
||||
|
||||
## 关于 {% data variables.product.prodname_codespaces %} 预构建的计费
|
||||
|
||||
{% data reusables.codespaces.billing-for-prebuilds-default %} 有关 {% data variables.product.prodname_codespaces %} 存储定价的详细信息，请参阅“[关于 {% data variables.product.prodname_github_codespaces %} 的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)”。
|
||||
|
|
@ -32,15 +40,15 @@ When prebuilds are available for a particular branch of a repository, a particul
|
|||
|
||||
## 关于将更改推送到启用了预构建的分支
|
||||
|
||||
默认情况下，每次推送到具有预构建配置的分支都会导致运行 {% data variables.product.prodname_dotcom %} 管理的 Actions 工作流程来更新预构建模板。 对于给定的预构建配置，预构建工作流程的并发限制为一次运行一个工作流程，除非所做的更改会影响关联存储库的开发容器配置。 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”。 如果运行已在进行中，则最近排队的工作流程运行将在当前运行完成后运行。
|
||||
By default, each push to a branch that has a prebuild configuration results in a {% data variables.product.prodname_dotcom %}-managed Actions workflow run to update the prebuild. 对于给定的预构建配置，预构建工作流程的并发限制为一次运行一个工作流程，除非所做的更改会影响关联存储库的开发容器配置。 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”。 如果运行已在进行中，则最近排队的工作流程运行将在当前运行完成后运行。
|
||||
|
||||
如果预构建模板设置为在每次推送时进行更新，这意味着当推送到存储库的频率很高时，预构建模板更新频率至少与运行预构建工作流程的频率相同。 也就是说，如果工作流程运行通常需要一个小时才能完成，当运行成功时，大约每小时为存储库创建预构建，当有更改分支上开发容器配置的推送时，则创建更为频繁。
|
||||
With the prebuild set to be updated on each push, it means that if there are very frequent pushes to your repository, prebuild updates will occur at least as often as it takes to run the prebuild workflow. 也就是说，如果工作流程运行通常需要一个小时才能完成，当运行成功时，大约每小时为存储库创建预构建，当有更改分支上开发容器配置的推送时，则创建更为频繁。
|
||||
|
||||
例如，假设对具有预构建配置的分支快速连续进行 5 次推送。 在此情况下：
|
||||
|
||||
* 将对第一次推送启动工作流程运行，以更新预构建模板。
|
||||
* A workflow run is started for the first push, to update the prebuild.
|
||||
* 如果剩余的 4 个推送不影响开发容器配置，则工作流程将针对这些推送在“挂起”状态下排队。
|
||||
|
||||
如果其余 4 个推送中的任何一个更改了开发容器配置，则服务不跳过该推送，而立即运行预构建创建工作流程，如果成功，则会相应地更新预构建。
|
||||
|
||||
* 第一次运行完成后，将为推送 2、3 和 4 运行工作流程，最后排队的工作流程（对于推送 5）将运行并更新预构建模板。
|
||||
* Once the first run completes, workflow runs for pushes 2, 3, and 4 will be canceled, and the last queued workflow (for push 5) will run and update the prebuild.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Allowing a prebuild to access other repositories
|
||||
shortTitle: Allow external repo access
|
||||
intro: 'You can permit your prebuild template access to other {% data variables.product.prodname_dotcom %} repositories so that it can be built successfully.'
|
||||
intro: 'You can permit your prebuild to access other {% data variables.product.prodname_dotcom %} repositories so that it can be built successfully.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
|
|
@ -55,7 +55,7 @@ You will need to create a new personal account and then use this account to crea
|
|||
1. 重新登录到对存储库具有管理员访问权限的帐户。
|
||||
1. 在要为其创建 {% data variables.product.prodname_codespaces %} 预构建的存储库中，创建一个名为 `CODESPACES_PREBUILD_TOKEN` 的新 {% data variables.product.prodname_codespaces %} 存储库机密，为其提供您创建和复制的令牌值。 更多信息请参阅“[管理用于 {% data variables.product.prodname_github_codespaces %} 的仓库和组织的加密密钥](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)”。
|
||||
|
||||
PAT 将用于为存储库创建的所有后续预构建模板。 与其他 {% data variables.product.prodname_codespaces %} 存储库机密不同， `CODESPACES_PREBUILD_TOKEN` 机密仅用于预构建，不可用于从存储库创建的代码空间。
|
||||
The PAT will be used for all subsequent prebuilds created for your repository. 与其他 {% data variables.product.prodname_codespaces %} 存储库机密不同， `CODESPACES_PREBUILD_TOKEN` 机密仅用于预构建，不可用于从存储库创建的代码空间。
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ permissions: People with admin access to a repository can configure prebuilds fo
|
|||
|
||||
You can set up a prebuild configuration for the combination of a specific branch of your repository with a specific dev container configuration file.
|
||||
|
||||
Any branches created from a prebuild-enabled parent branch will typically also get prebuilds for the same dev container configuration. This is because the prebuild template for child branches that use the same dev container configuration as the parent branch are, for the most part, identical, so developers can benefit from faster codespace creation times on those branches also. 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”。
|
||||
Any branches created from a prebuild-enabled parent branch will typically also get prebuilds for the same dev container configuration. This is because the prebuild for child branches that use the same dev container configuration as the parent branch are, for the most part, identical, so developers can benefit from faster codespace creation times on those branches also. 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”。
|
||||
|
||||
Typically, when you configure prebuilds for a branch, prebuilds will be available for multiple machine types. 但是，如果存储库大于 32 GB，则预构建将不适用于 2 核和 4 核计算机类型，因为它们提供的存储限制为 32 GB。
|
||||
|
||||
|
|
@ -44,37 +44,37 @@ Typically, when you configure prebuilds for a branch, prebuilds will be availabl
|
|||
|
||||
{% endnote %}
|
||||
|
||||
1. Optionally, in the **Configuration file** drop-down menu that's displayed, choose the `devcontainer.json` configuration file that you want to use for this prebuild template. 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)”。
|
||||
1. Optionally, in the **Configuration file** drop-down menu that's displayed, choose the `devcontainer.json` configuration file that you want to use for this prebuild. 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)”。
|
||||
|
||||
|
||||
|
||||
1. 选择自动触发预构建模板更新的方式。
|
||||
1. Choose how you want to automatically trigger updates of the prebuild.
|
||||
|
||||
* **每次推送**（默认设置）- 使用此设置，每次推送到给定分支时，都会更新预构建配置。 这将确保从预构建模板生成的代码空间始终包含最新的代码空间配置，包括任何最近添加或更新的依赖项。
|
||||
* **在配置更改时** - 使用此设置，每次更新给定存储库和分支的关联配置文件时，都会更新预构建配置。 这可确保在从预构建模板生成代码空间时使用对存储库的开发容器配置文件所做的更改。 更新预构建模板的 Actions 工作流程的运行频率较低，因此此选项将使用较少的 Actions 分钟数。 但是，此选项不保证代码空间始终包含最近添加或更新的依赖项，因此在创建代码空间后，可能必须手动添加或更新这些依赖项。
|
||||
* **每次推送**（默认设置）- 使用此设置，每次推送到给定分支时，都会更新预构建配置。 This will ensure that codespaces generated from a prebuild always contain the latest codespace configuration, including any recently added or updated dependencies.
|
||||
* **在配置更改时** - 使用此设置，每次更新给定存储库和分支的关联配置文件时，都会更新预构建配置。 This ensures that changes to the dev container configuration files for the repository are used when a codespace is generated from a prebuild. The Actions workflow that updates the prebuild will run less often, so this option will use fewer Actions minutes. 但是，此选项不保证代码空间始终包含最近添加或更新的依赖项，因此在创建代码空间后，可能必须手动添加或更新这些依赖项。
|
||||
* **计划** - 使用此设置，您可以按照自己定义的自定义计划更新预构建配置。 这可以减少操作分钟数的消耗，但是，使用此选项，可以创建不使用最新开发容器配置更改的代码空间。
|
||||
|
||||
|
||||
|
||||
1. Optionally, select **Reduce prebuild available to only specific regions** to limit access to your prebuild template, then select which regions you want it to be available in. 开发人员只能从预构建创建代码空间（如果它们位于所选区域中）。 By default, your prebuild template is available to all regions where codespaces is available and storage costs apply for each region.
|
||||
1. Optionally, select **Reduce prebuild available to only specific regions** to limit access to your prebuild, then select which regions you want it to be available in. 开发人员只能从预构建创建代码空间（如果它们位于所选区域中）。 By default, your prebuild is available to all regions where codespaces is available and storage costs apply for each region.
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**注意**：
|
||||
* 每个区域的预构建模板将产生单独的费用。 因此，您应仅为已知将使用预构建的区域启用预构建。 更多信息请参阅“[关于 {% data variables.product.prodname_github_codespaces %} 预构建](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)”。
|
||||
* The prebuild for each region will incur individual charges. 因此，您应仅为已知将使用预构建的区域启用预构建。 更多信息请参阅“[关于 {% data variables.product.prodname_github_codespaces %} 预构建](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)”。
|
||||
* 开发人员可以为 {% data variables.product.prodname_codespaces %} 设置其默认区域，这样您就可以为较少的区域启用预构建。 有关详细信息，请参阅“[设置 {% data variables.product.prodname_github_codespaces %} 的默认区域](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)”。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Optionally, set the number of prebuild template versions to be retained. 您可以输入 1 到 5 之间的任意数字。 保存版本的默认数量为 2，这意味着仅保存最新的模板版本和以前的版本。
|
||||
1. Optionally, set the number of prebuild versions to be retained. 您可以输入 1 到 5 之间的任意数字。 保存版本的默认数量为 2，这意味着仅保存最新的模板版本和以前的版本。
|
||||
|
||||
根据预构建触发器设置，预构建模板可能会随每次推送或每次开发容器配置更改而更改。 通过保留旧版本的预构建模板，可以从较旧的提交创建预构建，其开发容器配置与当前预构建模板不同。 由于保留预构建模板版本会产生相关的存储成本，因此您可以根据团队的需求选择要保留的版本数。 有关计费的更多信息，请参阅“[关于 {% data variables.product.prodname_github_codespaces %} 的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)”。
|
||||
Depending on your prebuild trigger settings, your prebuild could change with each push or on each dev container configuration change. Retaining older versions of prebuilds enables you to create a prebuild from an older commit with a different dev container configuration than the current prebuild. Since there is a storage cost associated with retaining prebuild versions, you can choose the number of versions to be retained based on the needs of your team. 有关计费的更多信息，请参阅“[关于 {% data variables.product.prodname_github_codespaces %} 的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)”。
|
||||
|
||||
如果要保存的预构建模板版本数设置为 1，{% data variables.product.prodname_codespaces %} 将仅保存预构建模板的最新版本，并在每次更新模板时删除旧版本。 这意味着，如果返回到较旧的开发容器配置，则不会获得预构建的代码空间。
|
||||
If you set the number of prebuild versions to save to 1, {% data variables.product.prodname_codespaces %} will only save the latest version of the prebuild and will delete the older version each time the template is updated. 这意味着，如果返回到较旧的开发容器配置，则不会获得预构建的代码空间。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Optionally, add users or teams to notify when the prebuild workflow run fails for this configuration. 您可以开始键入用户名、团队名称或全名，然后在出现名称后点按该名称以将其添加到列表中。 发生预构建失败时，您添加的用户或团队将收到一封电子邮件，其中包含指向工作流程运行日志的链接，以帮助进一步调查。
|
||||
|
||||
|
|
@ -84,7 +84,7 @@ Typically, when you configure prebuilds for a branch, prebuilds will be availabl
|
|||
|
||||
{% data reusables.codespaces.prebuilds-permission-authorization %}
|
||||
|
||||
After you create a prebuild configuration it is listed on the {% data variables.product.prodname_codespaces %} page of your repository settings. A {% data variables.product.prodname_actions %} workflow is queued and then run to create prebuild templates in the regions you specified, based on the branch and dev container configuration file you selected.
|
||||
After you create a prebuild configuration it is listed on the {% data variables.product.prodname_codespaces %} page of your repository settings. A {% data variables.product.prodname_actions %} workflow is queued and then run to create prebuilds in the regions you specified, based on the branch and dev container configuration file you selected.
|
||||
|
||||
|
||||
|
||||
|
|
@ -100,9 +100,9 @@ Prebuilds cannot use any user-level secrets while building your environment, bec
|
|||
|
||||
## 配置要包含在预构建中的耗时任务
|
||||
|
||||
您可以在 `devcontainer.json` 中使用 `onCreateCommand` 和 `updateContentCommand` 命令，以将耗时的过程作为预构建模板创建的一部分包括在内。 更多信息请参阅 {% data variables.product.prodname_vscode %} 文档“[devcontainer.json 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)”。
|
||||
You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild creation. 更多信息请参阅 {% data variables.product.prodname_vscode %} 文档“[devcontainer.json 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)”。
|
||||
|
||||
`onCreateCommand` 仅在创建预构建模板时运行一次，而 `updateContentCommand` 在模板创建和后续模板更新时运行。 增量构建应包含在 `updateContentCommand` 中，因为它们表示项目的源代码，并且需要包含在每个预构建模板更新中。
|
||||
`onCreateCommand` is run only once, when the prebuild is created, whereas `updateContentCommand` is run at template creation and at subsequent template updates. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild update.
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ miniTocMaxHeadingLevel: 3
|
|||
|
||||
您为存储库配置的预构建是使用 {% data variables.product.prodname_actions %} 工作流程创建和更新的，由 {% data variables.product.prodname_github_codespaces %} 服务管理。
|
||||
|
||||
根据预构建配置中的设置，更新预构建模板的工作流程可能由以下事件触发：
|
||||
Depending on the settings in a prebuild configuration, the workflow to update the prebuild may be triggered by these events:
|
||||
|
||||
* 创建或更新预构建配置
|
||||
* 将提交或拉取请求推送到配置为具有预构建的分支
|
||||
|
|
@ -24,7 +24,7 @@ miniTocMaxHeadingLevel: 3
|
|||
* 在预构建配置中定义的计划
|
||||
* 手动触发工作流程
|
||||
|
||||
预构建配置中的设置确定哪些事件会自动触发预构建模板的更新。 更多信息请参阅“[配置预构建](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)”。
|
||||
The settings in the prebuild configuration determine which events automatically trigger an update of the prebuild. 更多信息请参阅“[配置预构建](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)”。
|
||||
|
||||
对存储库具有管理员访问权限的人员可以检查预构建、编辑和删除预构建配置的进度。
|
||||
|
||||
|
|
@ -61,7 +61,7 @@ miniTocMaxHeadingLevel: 3
|
|||
|
||||
### 禁用预构建配置
|
||||
|
||||
要暂停更新配置的预构建模板，可以禁用配置的工作流程运行。 为预构建配置禁用工作流程不会删除以前为该配置创建的任何预构建模板，因此，代码空间将继续从现有预构建模板生成。
|
||||
To pause the update of prebuilds for a configuration, you can disable workflow runs for the configuration. Disabling the workflow runs for a prebuild configuration does not delete any previously created prebuilds for that configuration and, as a result, codespaces will continue to be generated from an existing prebuild.
|
||||
|
||||
如果需要调查模板创建失败，则禁用工作流程运行预构建配置非常有用。
|
||||
|
||||
|
|
@ -74,7 +74,7 @@ miniTocMaxHeadingLevel: 3
|
|||
|
||||
### 删除预构建配置
|
||||
|
||||
删除预构建配置也会删除以前为该配置创建的所有预构建模板。 因此，在删除配置后不久，在创建新代码空间时，由该配置生成的预构建将不再可用。
|
||||
Deleting a prebuild configuration also deletes all previously created prebuilds for that configuration. 因此，在删除配置后不久，在创建新代码空间时，由该配置生成的预构建将不再可用。
|
||||
|
||||
删除预构建配置后，该配置已排队或已启动的工作流程运行仍将运行。 它们将与以前完成的工作流程运行一起列在工作流程运行历史记录中。
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ product: '{% data reusables.gated-features.codespaces %}'
|
|||
permissions: People with write permissions to a repository can create or edit the dev container configuration for a branch.
|
||||
---
|
||||
|
||||
对启用了预构建的分支的开发容器配置所做任何更改，都将导致代码空间配置和关联的预构建模板更新。 因此，在将更改提交到当前使用的存储库分支之前，在代码空间中从测试分支测试此类更改非常重要。 这将确保您不会为团队引入破坏性更改。
|
||||
Any changes you make to the dev container configuration for a prebuild-enabled branch will result in an update to the codespace configuration and the associated prebuild. 因此，在将更改提交到当前使用的存储库分支之前，在代码空间中从测试分支测试此类更改非常重要。 这将确保您不会为团队引入破坏性更改。
|
||||
|
||||
更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”。
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ permissions: People with write permissions to a repository can create or edit th
|
|||
1. 在代码空间中，检出测试分支。 更多信息请参阅“[在代码空间中使用源控制](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches)”。
|
||||
1. 对开发容器配置进行所需的更改。
|
||||
1. 通过重新构建容器来应用更改。 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)”。
|
||||
1. 在一切正常之后，我们还建议从测试分支创建一个新的代码空间，以确保一切正常。 然后，您可以将更改提交到存储库的默认分支或活动功能分支，从而触发该分支的预构建模板的更新。
|
||||
1. 在一切正常之后，我们还建议从测试分支创建一个新的代码空间，以确保一切正常。 You can then commit your changes to your repository's default branch, or an active feature branch, triggering an update of the prebuild for that branch.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME
|
|||
|
||||
您可能会注意到，有时，当您从启用了预构建的分支创建新代码空间时，“{% octicon "zap" aria-label="The zap icon" %} 预构建就绪”标签不会显示在用于选择计算机类型的对话框中。 这意味着预构建当前不可用。
|
||||
|
||||
默认情况下，每次推送到启用了预构建的分支时，都会更新预构建模板。 如果推送涉及对开发容器配置的更改，则在更新过程中，将从计算机类型列表中删除“{% octicon "zap" aria-label="The zap icon" %} 预构建就绪”标签。 在此期间，您仍然可以在没有预构建模板的情况下创建代码空间。 如果需要，可以通过将预构建模板设置为仅在更改开发容器配置文件时更新或仅按自定义计划更新，从而减少存储库无法使用预构建的情况。 更多信息请参阅“[配置预构建](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)”。
|
||||
By default, each time you push to a prebuild-enabled branch, the prebuild is updated. 如果推送涉及对开发容器配置的更改，则在更新过程中，将从计算机类型列表中删除“{% octicon "zap" aria-label="The zap icon" %} 预构建就绪”标签。 During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. 更多信息请参阅“[配置预构建](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)”。
|
||||
|
||||
如果您的分支未专门为预构建启用，当它是启用了预构建的分支的分支时，也可从预构建受益。 但是，如果分支上的开发容器配置发生更改，使其与基本分支上的配置不同，则预构建在分支上将不再可用。
|
||||
|
||||
|
|
|
|||
|
|
@ -63,6 +63,7 @@ childGroups:
|
|||
- repositories
|
||||
- pull-requests
|
||||
- discussions
|
||||
- copilot
|
||||
- name: CI/CD and DevOps
|
||||
octicon: GearIcon
|
||||
children:
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ shortTitle: Display a sponsor button
|
|||
|
||||
You can configure your sponsor button by editing a _FUNDING.yml_ file in your repository's `.github` folder, on the default branch. You can configure the button to include sponsored developers in {% data variables.product.prodname_sponsors %}, external funding platforms, or a custom funding URL. For more information about {% data variables.product.prodname_sponsors %}, see "[About GitHub Sponsors](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)."
|
||||
|
||||
You can add one username, package name, or project name per external funding platform and up to four custom URLs. You can add up to four sponsored developers or organizations in {% data variables.product.prodname_sponsors %}. Add each platform on a new line, using the following syntax:
|
||||
You can add one username, package name, or project name per external funding platform and up to four custom URLs. You can add one organization and up to four sponsored developers in {% data variables.product.prodname_sponsors %}. Add each platform on a new line, using the following syntax:
|
||||
|
||||
Platform | Syntax
|
||||
-------- | -----
|
||||
|
|
|
|||
|
|
@ -0,0 +1,20 @@
|
|||
---
|
||||
title: Deployment branch policies
|
||||
allowTitleToDifferFromFilename: true
|
||||
shortTitle: Deployment branch policies
|
||||
intro: The Deployment branch policies API allows you to manage custom deployment branch policies.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
---
|
||||
|
||||
## About the Deployment branch policies API
|
||||
|
||||
The Deployment branch policies API allows you to specify custom name patterns that branches must match in order to deploy to an environment. The `deployment_branch_policy.custom_branch_policies` property for the environment must be set to `true` to use these endpoints. To update the `deployment_branch_policy` for an environment, see "[Create or update an environment](/rest/deployments/environments#create-or-update-an-environment)."
|
||||
|
||||
For more information about restricting environment deployments to certain branches, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment#deployment-branches)."
|
||||
|
|
@ -14,6 +14,7 @@ children:
|
|||
- /deployments
|
||||
- /environments
|
||||
- /statuses
|
||||
- /branch-policies
|
||||
redirect_from:
|
||||
- /rest/reference/deployments
|
||||
---
|
||||
|
|
|
|||
|
|
@ -314,8 +314,8 @@ CCPA 为加州居民提供关于其个人信息的某些权利。 要提交基
|
|||
#### 不受歧视的权利。
|
||||
您有权不因行使 CCPA 权利而受到歧视。 我们不会因您行使 CCPA 权利而歧视您。
|
||||
|
||||
您可以书面或通过授权书指定授权代理人代表您提出请求，以行使您在 CCPA 下的权利。 在接受代理商的此类请求之前，我们将要求代理商提供您授权其代表您行事的证明，并且我们可能需要您直接向我们验证您的身份。 此外，要提供或删除特定的个人信息，我们需要在法律要求的确定程度上验证您的身份。 我们将通过要求您从与您的帐户关联的电子邮件地址提交请求，或要求您提供验证帐户所需的信息，以验证您的请求。 [请注意，您可以在 GitHub 帐户中使用双因素身份验证。](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication)
|
||||
最后，您有权在收集个人信息时或之前收到有关我们做法的通知。
|
||||
您可以书面或通过授权书指定授权代理人代表您提出请求，以行使您在 CCPA 下的权利。 在接受代理商的此类请求之前，我们将要求代理商提供您授权其代表您行事的证明，并且我们可能需要您直接向我们验证您的身份。 此外，要提供或删除特定的个人信息，我们需要在法律要求的确定程度上验证您的身份。 我们将通过要求您从与您的帐户关联的电子邮件地址提交请求，或要求您提供验证帐户所需的信息，以验证您的请求。 [Please note that you may use two-factor authentication with your GitHub account](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication).
|
||||
Finally, you have a right to receive notice of our practices at or before collection of personal information.
|
||||
|
||||
此外，根据《加利福尼亚州民法典》第 1798.83 条（也称为“闪耀之光”法律），出于个人、家族或家庭目的向与该个人建立业务关系的企业提供个人信息的加利福尼亚州居民（“加州客户”），可以要求提供有关该企业是否已出于第三方的直接营销目的向任何第三方披露个人信息的信息。 请注意，我们不会向任何第三方披露个人信息，以用于本法规定的直接营销目的。 加州客户可以通过发送电子邮件到 **(privacy [at] github [dot] com)**索取有关我们遵守本法律的更多信息。 请注意，企业每年必须回复每位加州客户的一个请求，并且可能不需要回复通过指定电子邮件地址以外的方式提出的请求。
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,5 @@
|
|||
#Secret scanning: custom pattern dry run GA #7527
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-7527'
|
||||
|
|
@ -3,6 +3,5 @@
|
|||
##6367: updates for the "organization level dry runs (Public Beta)"
|
||||
##5499: updates for the "repository level dry runs (Public Beta)"
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>3.4'
|
||||
ghes: '>3.4 <3.7'
|
||||
ghae: 'issue-6367'
|
||||
|
|
|
|||
|
|
@ -3,6 +3,5 @@
|
|||
##6904: updates for "enterprise account level dry runs (Public Beta)"
|
||||
##7297: updates for dry runs on editing patterns (Public Beta)
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>3.5'
|
||||
ghes: '>3.5 <3.7'
|
||||
ghae: 'issue-6904'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#TOTP and mobile challenge for sudo mode prompt.
|
||||
versions:
|
||||
#fpt: '*'
|
||||
#ghec: '*'
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>= 3.7'
|
||||
|
|
|
|||
|
|
@ -1 +1,6 @@
|
|||
A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 30 days.
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 %}
|
||||
A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 14 days.
|
||||
An ephemeral self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 1 day.
|
||||
{%- elsif ghae or ghes < 3.7 %}
|
||||
A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 30 days.
|
||||
{%- endif %}
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
1. 试运行完成后，您将看到结果样本（最多 1000 个）。 查看结果并确定任何误报结果。 
|
||||
1. 编辑新的自定义模式以修复结果的任何问题，然后，若要测试更改，请单击 **Save and dry run（保存并试运行）**。
|
||||
{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,7 @@
|
|||
{%- ifversion custom-pattern-dry-run-ga %}
|
||||
1. Search for and select up to 10 repositories where you want to perform the dry run. 
|
||||
1. When you're ready to test your new custom pattern, click **Run**.
|
||||
{%- else %}
|
||||
1. Search for and select up to 10 repositories where you want to perform the dry run. 
|
||||
1. 当您准备好测试新的自定义模式时，请单击 **Dry run（试运行）**。
|
||||
{%- endif %}
|
||||
|
|
@ -1,2 +1,9 @@
|
|||
{%- ifversion custom-pattern-dry-run-ga %}
|
||||
1. Select the repositories where you want to perform the dry run.
|
||||
* To perform the dry run across the entire organization, select **All repositories in the organization**. 
|
||||
* To specify the repositories where you want to perform the dry run, select **Selected repositories**, then search for and select up to 10 repositories. 
|
||||
1. When you're ready to test your new custom pattern, click **Run**.
|
||||
{%- else %}
|
||||
1. Search for and select up to 10 repositories where you want to perform the dry run. 
|
||||
1. 当您准备好测试新的自定义模式时，请单击 **Dry run（试运行）**。
|
||||
{%- endif %}
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
默认情况下，每次创建或更新预构建模板或推送到启用了预构建的分支时，都会触发 {% data variables.product.prodname_actions %} 工作流程。 与其他工作流程一样，在预构建工作流程运行时，它们将消耗帐户中包含的一些操作分钟数（如果有），或者产生操作分钟数的费用。 有关操作分钟数定价的详细信息，请参阅[关于 {% data variables.product.prodname_actions %} 计费](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)”。
|
||||
By default, a {% data variables.product.prodname_actions %} workflow is triggered every time you create or update a prebuild, or push to a prebuild-enabled branch. 与其他工作流程一样，在预构建工作流程运行时，它们将消耗帐户中包含的一些操作分钟数（如果有），或者产生操作分钟数的费用。 有关操作分钟数定价的详细信息，请参阅[关于 {% data variables.product.prodname_actions %} 计费](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)”。
|
||||
|
||||
除了 {% data variables.product.prodname_actions %} 分钟数外，您还需要为存储与给定存储库和区域的每个预构建配置关联的预构建模板付费。 预构建模板的存储按与代码空间存储相同的费率计费。
|
||||
Alongside {% data variables.product.prodname_actions %} minutes, you will also be billed for the storage of prebuilds associated with each prebuild configuration for a given repository and region. Storage of prebuilds is billed at the same rate as storage of codespaces.
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
若要减少操作分钟数的消耗，可以将预构建模板设置为仅在对开发容器配置文件进行更改时更新，或仅按自定义计划进行更新。 您还可以通过调整要为预构建配置保留的模板版本数来管理存储使用情况。 更多信息请参阅“[配置预构建](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)”。
|
||||
To reduce consumption of Actions minutes, you can set a prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. 您还可以通过调整要为预构建配置保留的模板版本数来管理存储使用情况。 更多信息请参阅“[配置预构建](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)”。
|
||||
|
||||
如果您是组织所有者，则可以通过下载组织的 {% data variables.product.prodname_actions %} 使用情况报告来跟踪预构建工作流程和存储的使用情况。 You can identify workflow runs for prebuilds by filtering the CSV output to only include the workflow called "Create {% data variables.product.prodname_codespaces %} Prebuilds." 更多信息请参阅“[查看 {% data variables.product.prodname_actions %} 使用情况](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)”。
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
所有产品的**公共**仓库提供环境、环境保护规则和环境机密。 For access to environments in **private** or **internal** repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %}
|
||||
Environments, environment secrets, and environment protection rules are available in **public** repositories for all products. For access to environments, environment secrets, and deployment branches in **private** or **internal** repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_enterprise %}. For access to other environment protection rules in **private** or **internal** repositories, you must use {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %}
|
||||
|
|
|
|||
|
|
@ -71,7 +71,11 @@ PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %}
|
|||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
|
||||
PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
|
||||
Plivo | Plivo Auth ID with Plivo Auth Token | plivo_auth_id </br>plivo_auth_token{% endif %} Postman | Postman API Key | postman_api_key Proctorio | Proctorio Consumer Key | proctorio_consumer_key Proctorio | Proctorio Linkage Key | proctorio_linkage_key Proctorio | Proctorio Registration Key | proctorio_registration_key Proctorio | Proctorio Secret Key | proctorio_secret_key Pulumi | Pulumi Access Token | pulumi_access_token PyPI | PyPI API Token | pypi_api_token
|
||||
Plivo | Plivo Auth ID with Plivo Auth Token | plivo_auth_id </br>plivo_auth_token{% endif %} Postman | Postman API Key | postman_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
Prefect | Prefect Server API Key | prefect_server_api_key Prefect | Prefect User API Key | prefect_user_api_key{% endif %} Proctorio | Proctorio Consumer Key | proctorio_consumer_key Proctorio | Proctorio Linkage Key | proctorio_linkage_key Proctorio | Proctorio Registration Key | proctorio_registration_key Proctorio | Proctorio Secret Key | proctorio_secret_key Pulumi | Pulumi Access Token | pulumi_access_token PyPI | PyPI API Token | pypi_api_token
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
ReadMe | ReadMe API Access Key | readmeio_api_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %}
|
||||
redirect.pizza | redirect.pizza API 令牌 | redirect_pizza_api_token{% endif %} RubyGems | RubyGems API 密钥 | rubygems_api_key Samsara | Samsara API 令牌 | samsara_api_token Samsara | Samsara OAuth 访问令牌 | samsara_oauth_access_token
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
|
|
@ -96,6 +100,8 @@ Supabase | Supabase 服务密钥 | supabase_service_key{% endif %} Tableau | Tab
|
|||
Twilio | Twilio 访问令牌 | twilio_access_token{% endif %} Twilio | Twilio Account String 标识 | twilio_account_sid Twilio | Twilio API 密钥 | twilio_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Typeform | Typeform 个人访问令牌 | typeform_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
Uniwise | WISEflow API Key | wiseflow_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
WorkOS | WorkOS Production API 密钥 | workos_production_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
|
|
|
|||
|
|
@ -71,12 +71,15 @@
|
|||
| PlanetScale | PlanetScale 服务令牌 |
|
||||
| Plivo | Plivo 验证 ID 和令牌 |
|
||||
| Postman | Postman API 密钥 |
|
||||
| Prefect | Prefect Server API Key |
|
||||
| Prefect | Prefect User API Token |
|
||||
| Proctorio | Proctorio 消费者密钥 |
|
||||
| Proctorio | Proctorio 链接密钥 |
|
||||
| Proctorio | Proctorio 注册密钥 |
|
||||
| Proctorio | Proctorio 密钥 |
|
||||
| Pulumi | Pulumi 访问令牌 |
|
||||
| PyPI | PyPI API 令牌 |
|
||||
| ReadMe | ReadMe API Access Key |
|
||||
| redirect.pizza | redirect.pizza API 令牌 |
|
||||
| RubyGems | RubyGems API 密钥 |
|
||||
| Samsara | Samsara API 令牌 |
|
||||
|
|
@ -102,5 +105,6 @@
|
|||
| Twilio | Twilio 帐户字符串标识符 |
|
||||
| Twilio | Twilio API 密钥 |
|
||||
| Typeform | Typeform 个人访问令牌 |
|
||||
| Uniwise | WISEflow API Key |
|
||||
| Valour | Valour 访问令牌 |
|
||||
| Zuplo | Zuplo Consumer API |
|
||||
|
|
|
|||
|
|
@ -13,8 +13,14 @@
|
|||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
Azure | Azure Storage Account Key | azure_storage_account_key{% endif %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key Clojars | Clojars Deploy Token | clojars_deploy_token Databricks | Databricks Access Token | databricks_access_token DigitalOcean | DigitalOcean Personal Access Token | digitalocean_personal_access_token DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token DigitalOcean | DigitalOcean Refresh Token | digitalocean_refresh_token DigitalOcean | DigitalOcean System Token | digitalocean_system_token Discord | Discord Bot Token | discord_bot_token Doppler | Doppler Personal Token | doppler_personal_token Doppler | Doppler Service Token | doppler_service_token Doppler | Doppler CLI Token | doppler_cli_token Doppler | Doppler SCIM Token | doppler_scim_token Doppler | Doppler Audit Token | doppler_audit_token Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token Duffel | Duffel Live Access Token | duffel_live_access_token EasyPost | EasyPost Production API Key | easypost_production_api_key Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key Fullstory | FullStory API Key | fullstory_api_key GitHub | GitHub Personal Access Token | github_personal_access_token GitHub | GitHub OAuth Access Token | github_oauth_access_token GitHub | GitHub Refresh Token | github_refresh_token GitHub | GitHub App Installation Access Token | github_app_installation_access_token GitHub | GitHub SSH Private Key | github_ssh_private_key Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id </br>google_cloud_storage_access_key_secret Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id </br>google_cloud_storage_access_key_secret Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id </br>google_oauth_client_secret Grafana | Grafana API Key | grafana_api_key Hubspot | Hubspot API Key | hubspot_api_key Intercom | Intercom Access Token | intercom_access_token
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
JFrog | JFrog 平台访问令牌 | jfrog_platform_access_token JFrog | JFrog 平台 API 密钥 | jfrog_platform_api_key{% endif %} Ionic | Ionic 个人访问令牌 | ionic_personal_access_token Ionic | Ionic 刷新令牌 | ionic_refresh_token Linear | Linear API 密钥 | linear_api_key Linear | Linear OAuth 访问令牌 | linear_oauth_access_token Midtrans | Midtrans 生产服务器密钥 | midtrans_production_server_key New Relic | New Relic 个人 API 密钥 | new_relic_personal_api_key New Relic | New Relic REST API 密钥 | new_relic_rest_api_key New Relic | New Relic Insights 查询密钥 | new_relic_insights_query_key npm | npm 访问令牌 | npm_access_token NuGet | NuGet API 密钥 | nuget_api_key Onfido | Onfido Live API 令牌 | onfido_live_api_token OpenAI | OpenAI API 密钥 | openai_api_key PlanetScale | PlanetScale 数据库密码 | planetscale_database_password PlanetScale | PlanetScale OAuth 令牌 | planetscale_oauth_token PlanetScale | PlanetScale 服务令牌 | planetscale_service_token Postman | Postman API 密钥 | postman_api_key Proctorio | Proctorio 密钥 | proctorio_secret_key
|
||||
JFrog | JFrog Platform Access Token | jfrog_platform_access_token JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} Ionic | Ionic Personal Access Token | ionic_personal_access_token Ionic | Ionic Refresh Token | ionic_refresh_token Linear | Linear API Key | linear_api_key Linear | Linear OAuth Access Token | linear_oauth_access_token Midtrans | Midtrans Production Server Key | midtrans_production_server_key New Relic | New Relic Personal API Key | new_relic_personal_api_key New Relic | New Relic REST API Key | new_relic_rest_api_key New Relic | New Relic Insights Query Key | new_relic_insights_query_key npm | npm Access Token | npm_access_token NuGet | NuGet API Key | nuget_api_key Onfido | Onfido Live API Token | onfido_live_api_token OpenAI | OpenAI API Key | openai_api_key PlanetScale | PlanetScale Database Password | planetscale_database_password PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token PlanetScale | PlanetScale Service Token | planetscale_service_token Postman | Postman API Key | postman_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
Prefect | Prefect Server API Key | prefect_server_api_key Prefect | Prefect User API Key | prefect_user_api_key{% endif %} Proctorio | Proctorio Secret Key | proctorio_secret_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
ReadMe | ReadMe API Access Key | readmeio_api_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %}
|
||||
redirect.pizza | redirect.pizza API 令牌 | redirect_pizza_api_token{% endif %} Samsara | Samsara API 令牌 | samsara_api_token Samsara | Samsara OAuth 访问令牌 | samsara_oauth_access_token SendGrid | SendGrid API 密钥 | sendgrid_api_key Sendinblue | Sendinblue API 密钥 | sendinblue_api_key Sendinblue | Sendinblue SMTP 密钥 | sendinblue_smtp_key Shippo | Shippo Live API 令牌 | shippo_live_api_token Shopify | Shopify App 共享密钥 | shopify_app_shared_secret Shopify | Shopify 访问令牌 | shopify_access_token Slack | Slack API 令牌 | slack_api_token Stripe | Stripe Live API 密钥 | stripe_api_key Tencent Cloud | Tencent Cloud 密钥 ID | tencent_cloud_secret_id Typeform | Typeform 个人访问令牌 | typeform_personal_access_token WorkOS | WorkOS 生产 API 密钥 | workos_production_api_key
|
||||
redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %} Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token SendGrid | SendGrid API Key | sendgrid_api_key Sendinblue | Sendinblue API Key | sendinblue_api_key Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key Shippo | Shippo Live API Token | shippo_live_api_token Shopify | Shopify App Shared Secret | shopify_app_shared_secret Shopify | Shopify Access Token | shopify_access_token Slack | Slack API Token | slack_api_token Stripe | Stripe Live API Secret Key | stripe_api_key Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id Typeform | Typeform Personal Access Token | typeform_personal_access_token
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
Uniwise | WISEflow API Key | wiseflow_api_key{% endif %} WorkOS | WorkOS Production API Key | workos_production_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
Zuplo | Zuplo Consumer API 密钥 | zuplo_consumer_api_key{% endif %}
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. 将您的 GitHub 帐户与 Jira 链接。 更多信息请参阅 [Atlassian 的帮助文档](https://confluence.atlassian.com/adminjiracloud/connect-jira-cloud-to-github-814188429.html)。
|
||||
1. 将您的 GitHub 帐户与 Jira 链接。 For more information, see [Atlassian's help documentation](https://confluence.atlassian.com/adminjiracloud/connect-jira-cloud-to-github-814188429.html).
|
||||
|
|
|
|||
|
|
@ -7,8 +7,7 @@ header:
|
|||
notices:
|
||||
ghae_silent_launch: GitHub AE 目前是有限发行版。请<a href="https://enterprise.github.com/contact">联系我们的销售团队</a>以了解更多信息。
|
||||
release_candidate: '# 版本名称是通过 includes/header-notification.html 在以下文本之前呈现：目前可用作发行版候选。更多信息请参阅“<a href="/admin/overview/about-upgrades-to-new-releases">关于升级到新版本</a>”。'
|
||||
localization_complete: 我们经常发布文档更新，此页面的翻译可能仍在进行中。有关最新信息，请访问<a id="to-english-doc" href="/en">英文文档</a>。如果此页面上的翻译有问题，请<a href="https://github.com/contact?form[subject]=translation%20issue%20on%20docs.github.com&form[comments]=">告诉我们</a>。
|
||||
localization_in_progress: 你好，探索者！ 此页面正在积极开发或仍在翻译中。有关最新和最准确的信息，请访问我们的<a id="to-english-doc" href="/en">英文文档</a>。
|
||||
localization_complete: We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the <a id="to-english-doc" href="/en">English documentation</a>.
|
||||
early_access: '📣请<b>不要公开分享</b>此 URL，该页面包含有关早期访问功能的内容。'
|
||||
release_notes_use_latest: 请使用最新版本获取最新的安全性、性能和错误修复。
|
||||
#GHES release notes
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче