Octomerger Bot
@@ -310,7 +310,7 @@ 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/github-reviews-security-advisories.md,broken liquid tags
|
||||
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,rendering error
|
||||
translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags
|
||||
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/sponsors/feedback.md,broken liquid tags
|
||||
|
||||
|
@@ -24,7 +24,7 @@ To access your personal dashboard once you're signed in, click the {% octicon "m
|
||||
|
||||
## Finding your recent activity
|
||||
|
||||
In the "Recent activity" section of your news feed, you can quickly find and follow up with recently updated issues and pull requests you're working on. Under "Recent activity", you can preview up to 12 recent updates made in the last two weeks.
|
||||
In the "Recent activity" section of your news feed, you can quickly find and follow up with recently updated issues and pull requests you're working on. Under "Recent activity", you can preview up to 4 recent updates made in the last two weeks.
|
||||
|
||||
{% data reusables.dashboard.recent-activity-qualifying-events %}
|
||||
|
||||
|
||||
@@ -20,14 +20,6 @@ shortTitle: 管理主题设置
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}如果您视力不佳，则可以从前景和背景元素之间对比度更高的高对比度主题中受益。{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} 如果您有色盲，可能会从我们的浅色盲和深色盲主题中受益。
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
**注意：**色盲主题目前处于公开测试阶段。 有关在公开测试版中启用功能的更多信息，请参阅“[使用功能预览版探索抢先体验版本](/get-started/using-github/exploring-early-access-releases-with-feature-preview)”。
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
|
||||
@@ -65,7 +65,7 @@ jobs:
|
||||
|
||||
### 使用多个 Swift 版本
|
||||
|
||||
您可以将作业配置为在构建矩阵中使用多个版本的 Swift。
|
||||
You can configure your job to use multiple versions of Swift in a matrix.
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
@@ -23,7 +23,7 @@ miniTocMaxHeadingLevel: 3
|
||||
|
||||
上下文是一种访问工作流程运行、运行器环境、作业及步骤相关信息的方式。 每个上下文都是一个包含属性的对象，属性可以是字符串或其他对象。
|
||||
|
||||
{% data reusables.actions.context-contents %} 例如，`matrix` 上下文中仅填充 [build matrix](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix) 中的作业。
|
||||
{% data reusables.actions.context-contents %} For example, the `matrix` context is only populated for jobs in a [matrix](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
|
||||
|
||||
您可以使用表达式语法访问上下文。 更多信息请参阅“[表达式](/actions/learn-github-actions/expressions)”。
|
||||
|
||||
@@ -537,19 +537,19 @@ jobs:
|
||||
|
||||
## `strategy` 上下文
|
||||
|
||||
对于具有生成矩阵的工作流程，`strategy` 上下文包含有关当前作业的矩阵执行策略的信息。
|
||||
For workflows with a matrix, the `strategy` context contains information about the matrix execution strategy for the current job.
|
||||
|
||||
| 属性名称 | 类型 | 描述 |
|
||||
| ----------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `strategy` | `对象` | 此上下文针对工作流程运行中的每项作业而改变。 您可以从工作流程中的任何作业或步骤访问此上下文。 此对象包含下面列出的所有属性。 |
|
||||
| `strategy.fail-fast` | `字符串` | 为 `true` 时，如果构建矩阵中的任何作业失败，所有正在进行的作业都将被取消。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)”。 |
|
||||
| `strategy.job-index` | `字符串` | 生成矩阵中当前作业的索引。 **注意：** 此数字是零基数字。 生成矩阵中第一个作业的索引是 `0`。 |
|
||||
| `strategy.job-total` | `字符串` | 生成矩阵中的作业总数。 **注意：** 此数字 **不是**从零基数字。 例如，对于具有四个作业的生成矩阵，`job-total` 的值为 `4`。 |
|
||||
| `strategy.max-parallel` | `字符串` | 使用 `matrix` 作业策略时可同时运行的最大作业数。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel)”。 |
|
||||
| 属性名称 | 类型 | 描述 |
|
||||
| ----------------------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `strategy` | `对象` | 此上下文针对工作流程运行中的每项作业而改变。 您可以从工作流程中的任何作业或步骤访问此上下文。 此对象包含下面列出的所有属性。 |
|
||||
| `strategy.fail-fast` | `字符串` | When `true`, all in-progress jobs are canceled if any job in a matrix fails. 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)”。 |
|
||||
| `strategy.job-index` | `字符串` | The index of the current job in the matrix. **注意：** 此数字是零基数字。 The first job's index in the matrix is `0`. |
|
||||
| `strategy.job-total` | `字符串` | The total number of jobs in the matrix. **注意：** 此数字 **不是**从零基数字。 For example, for a matrix with four jobs, the value of `job-total` is `4`. |
|
||||
| `strategy.max-parallel` | `字符串` | 使用 `matrix` 作业策略时可同时运行的最大作业数。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel)”。 |
|
||||
|
||||
### `strategy` 上下文的示例内容
|
||||
|
||||
`strategy` 上下文的以下示例内容来自具有四个作业的生成矩阵，取自最终作业。 请注意零基 `job-index` 数字与 `job-total` （非零基）之间的差异。
|
||||
The following example contents of the `strategy` context is from a matrix with four jobs, and is taken from the final job. 请注意零基 `job-index` 数字与 `job-total` （非零基）之间的差异。
|
||||
|
||||
```yaml
|
||||
{
|
||||
@@ -562,7 +562,7 @@ jobs:
|
||||
|
||||
### `strategy` 上下文的示例用法
|
||||
|
||||
此示例工作流程使用 `strategy.job-index` 属性为生成矩阵中每个作业的日志文件设置唯一名称。
|
||||
This example workflow uses the `strategy.job-index` property to set a unique name for a log file for each job in a matrix.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Test matrix
|
||||
@@ -587,18 +587,18 @@ jobs:
|
||||
|
||||
## `matrix` 上下文
|
||||
|
||||
对于具有生成矩阵的工作流程，`matrix` 上下文包含工作流程文件中定义的适用于当前作业的矩阵属性。 例如，如果使用 `os` 和 `node` 键配置生成矩阵，则 `matrix` 上下文对象将包括 `os` 和 `node` 属性，具有用于当前作业的值。
|
||||
For workflows with a matrix, the `matrix` context contains the matrix properties defined in the workflow file that apply to the current job. For example, if you configure a matrix with the `os` and `node` keys, the `matrix` context object includes the `os` and `node` properties with the values that are being used for the current job.
|
||||
|
||||
`matrix` 上下文中没有标准属性，只有工作流程文件中定义的属性。
|
||||
|
||||
| 属性名称 | 类型 | 描述 |
|
||||
| ------------------------------ | ----- | ------------------------------------------------------------------------------ |
|
||||
| `matrix` | `对象` | 此上下文仅适用于生成矩阵中的作业，并且对于工作流运行中的每个作业都会发生更改。 您可以从工作流程中的任何作业或步骤访问此上下文。 此对象包含下面列出的属性。 |
|
||||
| `matrix.<property_name>` | `字符串` | 矩阵属性的值。 |
|
||||
| 属性名称 | 类型 | 描述 |
|
||||
| ------------------------------ | ----- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `matrix` | `对象` | This context is only available for jobs in a matrix, and changes for each job in a workflow run. 您可以从工作流程中的任何作业或步骤访问此上下文。 此对象包含下面列出的属性。 |
|
||||
| `matrix.<property_name>` | `字符串` | 矩阵属性的值。 |
|
||||
|
||||
### `matrix` 上下文的示例内容
|
||||
|
||||
`matrix` 上下文的以下示例内容来自生成矩阵中的作业，该生成矩阵具有工作流中定义的 `os` 和 `node` 矩阵属性。 该作业执行 `ubuntu-latest` OS 和 Node.js 版本 `16` 的矩阵组合。
|
||||
The following example contents of the `matrix` context is from a job in a matrix that has the `os` and `node` matrix properties defined in the workflow. 该作业执行 `ubuntu-latest` OS 和 Node.js 版本 `16` 的矩阵组合。
|
||||
|
||||
```yaml
|
||||
{
|
||||
@@ -609,7 +609,7 @@ jobs:
|
||||
|
||||
### `matrix` 上下文的示例用法
|
||||
|
||||
此示例工作流程创建一个包含 `os` 和 `node` 键的生成矩阵。 它使用 `matrix.os` 属性为每个作业设置运行器类型，并使用 `matrix.node` 属性为每个作业设置 Node.js 版本。
|
||||
This example workflow creates a matrix with `os` and `node` keys. 它使用 `matrix.os` 属性为每个作业设置运行器类型，并使用 `matrix.node` 属性为每个作业设置 Node.js 版本。
|
||||
|
||||
```yaml{:copy}
|
||||
name: Test matrix
|
||||
|
||||
@@ -50,7 +50,7 @@ CircleCI 和 {% data variables.product.prodname_actions %} 在配置文件中使
|
||||
|
||||
CircleCI 和 {% data variables.product.prodname_actions %} 都提供在工作流程中重复使用和共享任务的机制。 CircleCI 使用以 YAML 编写的概念 orbs 来提供人们可以在工作流程中重复使用的任务。 {% data variables.product.prodname_actions %} 具有强大而灵活的可重复使用的组件，称为“操作”，您可以使用 JavaScript 文件或 Docker 映像来构建操作。 您可以编写自定义代码来创建操作，以您喜欢的方式与仓库交互，包括使用 {% data variables.product.product_name %} 的 API 以及任何公开的第三方 API 进行交互。 例如，操作可以发布 npm 模块、在创建紧急议题时发送短信提醒，或者部署可用于生产的代码。 更多信息请参阅“[创建操作](/actions/creating-actions)”。
|
||||
|
||||
CircleCI 可以使用 YAML 锚点和别名来重复使用工作流程的组件。 {% data variables.product.prodname_actions %} 支持对于重复使用构建矩阵的最常见需求。 有关构建矩阵的更多信息，请参阅“[管理复杂的工作流程](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)”。
|
||||
CircleCI 可以使用 YAML 锚点和别名来重复使用工作流程的组件。 {% data variables.product.prodname_actions %} supports the most common need for reusability using matrices. For more information about matrices, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
## 使用 Docker 映像
|
||||
|
||||
|
||||
@@ -83,9 +83,9 @@ Jenkins 可以并行运行 `stages` 和 `steps`，而 {% data variables.product.
|
||||
| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [`parallel`](https://jenkins.io/doc/book/pipeline/syntax/#parallel) | [`jobs.<job_id>.strategy.max-parallel`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel) |
|
||||
|
||||
### 构建矩阵
|
||||
### Matrix
|
||||
|
||||
{% data variables.product.prodname_actions %} 和 Jenkins 都允许您使用构建矩阵来定义各种系统组合。
|
||||
Both {% data variables.product.prodname_actions %} and Jenkins let you use a matrix to define various system combinations.
|
||||
|
||||
| Jenkins | {% data variables.product.prodname_actions %}
|
||||
| ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
|
||||
@@ -59,9 +59,9 @@ Travis CI 可以使用 `stages` 并行运行作业。 同样，{% data variables
|
||||
|
||||
Travis CI 和 {% data variables.product.prodname_actions %} 都支持状态徽章，用于表示构建是通过还是失败。 更多信息请参阅“[将工作流程状态徽章添加到仓库](/actions/managing-workflow-runs/adding-a-workflow-status-badge)”。
|
||||
|
||||
### 使用构建矩阵
|
||||
### Using a matrix
|
||||
|
||||
Travis CI和 {% data variables.product.prodname_actions %} 都支持构建矩阵，允许您使用操作系统和软件包的组合进行测试。 更多信息请参阅“[使用构建矩阵](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)”。
|
||||
Travis CI and {% data variables.product.prodname_actions %} both support a matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
下面是比较每个系统的语法示例：
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ children:
|
||||
- /using-jobs-in-a-workflow
|
||||
- /choosing-the-runner-for-a-job
|
||||
- /using-conditions-to-control-job-execution
|
||||
- /using-a-build-matrix-for-your-jobs
|
||||
- /using-a-matrix-for-your-jobs
|
||||
- /using-concurrency
|
||||
- /using-environments-for-jobs
|
||||
- /running-jobs-in-a-container
|
||||
|
||||
@@ -1,30 +0,0 @@
|
||||
---
|
||||
title: 对作业使用构建矩阵
|
||||
shortTitle: 对作业使用构建矩阵
|
||||
intro: 创建构建矩阵并定义每个作业的变体。
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
miniTocMaxHeadingLevel: 4
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## 概览
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-strategy %}
|
||||
|
||||
## 创建不同作业配置的矩阵
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-matrix %}
|
||||
|
||||
## 在 `matrix` 作业失败时取消剩余作业
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-failfast %}
|
||||
|
||||
## 定义 `matrix` 中的最大并发作业数
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-max-parallel %}
|
||||
@@ -0,0 +1,60 @@
|
||||
---
|
||||
title: Using a matrix for your jobs
|
||||
shortTitle: Using a matrix
|
||||
intro: Create a matrix to define variations for each job.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
miniTocMaxHeadingLevel: 4
|
||||
redirect_from:
|
||||
- /actions/using-jobs/using-a-build-matrix-for-your-jobs
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## About matrix strategies
|
||||
|
||||
{% data reusables.actions.jobs.about-matrix-strategy %}
|
||||
|
||||
## Using a matrix strategy
|
||||
|
||||
{% data reusables.actions.jobs.using-matrix-strategy %}
|
||||
|
||||
### Example: Using a single-dimension matrix
|
||||
|
||||
{% data reusables.actions.jobs.single-dimension-matrix %}
|
||||
|
||||
### Example: Using a multi-dimension matrix
|
||||
|
||||
{% data reusables.actions.jobs.multi-dimension-matrix %}
|
||||
|
||||
### Example: Using contexts to create matrices
|
||||
|
||||
{% data reusables.actions.jobs.matrix-from-context %}
|
||||
|
||||
## Expanding or adding matrix configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-include %}
|
||||
|
||||
### Example: Expanding configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-expand-with-include %}
|
||||
|
||||
### Example: Adding configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-add-with-include %}
|
||||
|
||||
## Excluding matrix configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-exclude %}
|
||||
|
||||
## Handling failures
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-failfast %}
|
||||
|
||||
## Defining the maximum number of concurrent jobs
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-max-parallel %}
|
||||
@@ -105,9 +105,9 @@ jobs:
|
||||
|
||||
更多信息请参阅“[定义先决条件作业](/actions/using-jobs/using-jobs-in-a-workflow#defining-prerequisite-jobs)”。
|
||||
|
||||
### 使用构建矩阵
|
||||
### Using a matrix
|
||||
|
||||
如果您希望工作流程跨参数（如操作系统、平台和语言）的多个组合运行测试，可以使用构建矩阵。 构建矩阵是使用 `strategy` 关键字创建的，它接收构建选项作为数组。 例如，此构建矩阵将使用不同版本的 Node.js 多次运行作业：
|
||||
{% data reusables.actions.jobs.about-matrix-strategy %} The matrix is created using the `strategy` keyword, which receives the build options as an array. For example, this matrix will run the job multiple times, using different versions of Node.js:
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
@@ -115,14 +115,14 @@ jobs:
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
node: [6, 8, 10]
|
||||
node: [12, 14, 16]
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.node }}{% endraw %}
|
||||
```
|
||||
|
||||
更多信息请参阅“[对作业使用构建矩阵](/actions/using-jobs/using-a-build-matrix-for-your-jobs)”。
|
||||
For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### 缓存依赖项
|
||||
|
||||
@@ -745,11 +745,39 @@ steps:
|
||||
|
||||
## `jobs.<job_id>.strategy`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-strategy %}
|
||||
Use `jobs.<job_id>.strategy` to use a matrix strategy for your jobs. {% data reusables.actions.jobs.about-matrix-strategy %} For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
### `jobs.<job_id>.strategy.matrix`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-matrix %}
|
||||
{% data reusables.actions.jobs.using-matrix-strategy %}
|
||||
|
||||
#### Example: Using a single-dimension matrix
|
||||
|
||||
{% data reusables.actions.jobs.single-dimension-matrix %}
|
||||
|
||||
#### Example: Using a multi-dimension matrix
|
||||
|
||||
{% data reusables.actions.jobs.multi-dimension-matrix %}
|
||||
|
||||
#### Example: Using contexts to create matrices
|
||||
|
||||
{% data reusables.actions.jobs.matrix-from-context %}
|
||||
|
||||
### `jobs.<job_id>.strategy.matrix.include`
|
||||
|
||||
{% data reusables.actions.jobs.matrix-include %}
|
||||
|
||||
#### Example: Expanding configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-expand-with-include %}
|
||||
|
||||
#### Example: Adding configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-add-with-include %}
|
||||
|
||||
### `jobs.<job_id>.strategy.matrix.exclude`
|
||||
|
||||
{% data reusables.actions.jobs.matrix-exclude %}
|
||||
|
||||
### `jobs.<job_id>.strategy.fail-fast`
|
||||
|
||||
@@ -846,7 +874,7 @@ services:
|
||||
|
||||
### `jobs.<job_id>.services.<service_id>.image`
|
||||
|
||||
要用作运行操作的服务容器的 Docker 图像。 值可以是 Docker Hub 映像名称或注册表名称。
|
||||
要用作运行操作的服务容器的 Docker 镜像。 值可以是 Docker Hub 映像名称或注册表名称。
|
||||
|
||||
### `jobs.<job_id>.services.<service_id>.credentials`
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Using the audit log API for your enterprise
|
||||
intro: 'You can programmatically retrieve enterprise events with the{% ifversion ghec or ghes > 3.2 %} REST or{% endif %} GraphQL API.'
|
||||
shortTitle: Audit log API
|
||||
title: 使用企业的审核日志 API
|
||||
intro: '您可以使用{% ifversion ghec or ghes > 3.2 %} REST 或{% endif %} GraphQL API 以编程方式检索企业事件。'
|
||||
shortTitle: 审核日志 API
|
||||
permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can use the audit log API.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -20,23 +20,23 @@ topics:
|
||||
|
||||
您可以使用 GraphQL API{% ifversion ghec or ghes > 3.2 or ghae-issue-6648 %} 或 REST API{% endif %} 与审核日志交互。
|
||||
|
||||
Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time).
|
||||
API 响应中的时间戳和日期字段以 [UTC 纪元毫秒](http://en.wikipedia.org/wiki/Unix_time)为单位进行度量。
|
||||
|
||||
{% ifversion ghec or ghes > 3.0 or ghae %}
|
||||
## Querying the audit log GraphQL API
|
||||
## 查询审核日志 GraphQL API
|
||||
|
||||
To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log GraphQL API to keep copies of your audit log data and monitor:
|
||||
为确保知识产权得到保护并保持企业的合规，您可以使用审核日志 GraphQL API 保留审核日志数据的副本并监控：
|
||||
{% data reusables.audit_log.audit-log-api-info %}
|
||||
|
||||
Note that you can't retrieve Git events using the {% ifversion not ghec %}audit log API.{% else %}GraphQL API. 要检索 Git 事件，请改为使用 REST API。 For more information, see `git` category actions in "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)", and also the "[Enterprise administration](/rest/reference/enterprise-admin#audit-log)" and "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization) audit log endpoints in the REST API documentation."{% endif %}
|
||||
请注意，无法使用 {% ifversion not ghec %}审核日志 API{% else %}GraphQL API 检索 Git 事件。 要检索 Git 事件，请改为使用 REST API。 更多信息请参阅“[审核企业的日志操作](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)”中的 `git` 类操作，以及 REST API 文档中的“[企业管理](/rest/reference/enterprise-admin#audit-log)”和“[组织](/rest/reference/orgs#get-the-audit-log-for-an-organization)审核日志端点”。{% endif %}
|
||||
|
||||
GraphQL 响应可包含长达 90 至 120 天的数据。
|
||||
|
||||
### Example 1: Members added to or removed from organizations in an enterprise
|
||||
### 示例 1：在企业中的组织中添加或删除的成员
|
||||
|
||||
The query below fetches the audit logs for the `avocado-corp` enterprise and returns the first 10 organizations in the enterprise, where the only actions performed were adding or removing a member from an organization. The first 20 audit log entries for each organization are returned.
|
||||
下面的查询获取 `avocado-corp` 企业的审核日志，并返回企业中的前 10 个组织，其中执行的唯一操作是在组织中添加或删除成员。 将返回每个组织的前 20 个审核日志条目。
|
||||
|
||||
This query uses the [auditlog](/graphql/reference/objects) field from the Organization object, and the [OrgAddMemberAuditEntry](/graphql/reference/objects#orgaddmemberauditentry) and [OrgRemoveMemberAuditEntry](/graphql/reference/objects#orgremovememberauditentry) objects. The {% data variables.product.prodname_dotcom %} account querying the enterprise audit log must be an organization owner for each organization within the enterprise.
|
||||
此查询使用组织对象中的 [auditlog](/graphql/reference/objects) 字段，以及 [OrgAddMemberAuditEntry](/graphql/reference/objects#orgaddmemberauditentry) 和 [OrgRemoveMemberAuditEntry](/graphql/reference/objects#orgremovememberauditentry) 对象。 查询企业审核日志的 {% data variables.product.prodname_dotcom %} 帐户必须是企业内每个组织的组织所有者。
|
||||
|
||||
```shell
|
||||
{
|
||||
@@ -70,14 +70,14 @@ This query uses the [auditlog](/graphql/reference/objects) field from the Organi
|
||||
}
|
||||
```
|
||||
|
||||
The GraphQL API will return at most 100 nodes per query. To retrieve additional results, you'll need to implement pagination. For more information, see "[Resource limitations](/graphql/overview/resource-limitations#node-limit)" in the GraphQL API documentation and [Pagination](https://graphql.org/learn/pagination/) in the official GraphQL documentation.
|
||||
### Example 2: Events in an organization, for a specific date and actor
|
||||
GraphQL API 对每个查询最多返回 100 个节点。 要检索其他结果，需要实现分页。 更多信息请参阅 GraphQL API 文档中的“[资源限制](/graphql/overview/resource-limitations#node-limit)”和官方 GraphQL 文档中的[分页](https://graphql.org/learn/pagination/)。
|
||||
### 示例 2：组织中特定日期和参与者的事件
|
||||
|
||||
You can specify multiple search phrases, such as `created` and `actor`, by separating them in your query string with a space.
|
||||
您可以通过在查询字符串中用空格分隔多个搜索短语（ 如 `created` 和 `actor`）来指定这些搜索短语。
|
||||
|
||||
The query below fetches all the audit logs for the `avocado-corp` enterprise that relate to the `octo-org` organization, where the actions were performed by the `octocat` user on or after the 1 Jan, 2022. The first 20 audit log entries are returned, with the newest log entry appearing first.
|
||||
下面的查询获取与 `octo-org` 组织相关的 `avocado-corp` 企业的所有审核日志，其中操作由 `octocat` 用户在 2022 年 1 月 1 日当天或之后执行。 将返回前 20 个审核日志条目，最新的日志条目首先显示。
|
||||
|
||||
This query uses the [AuditEntry](/graphql/reference/interfaces#auditentry) interface. The {% data variables.product.prodname_dotcom %} account querying the enterprise audit log must be an owner of the `octo-org` organization.
|
||||
此查询使用 [AuditEntry](/graphql/reference/interfaces#auditentry) 接口。 查询企业审核日志的 {% data variables.product.prodname_dotcom %} 帐户必须是 `octo-org` 组织的所有者。
|
||||
|
||||
```shell
|
||||
{
|
||||
@@ -105,22 +105,22 @@ This query uses the [AuditEntry](/graphql/reference/interfaces#auditentry) inter
|
||||
}
|
||||
```
|
||||
|
||||
For more query examples, see the [platform-samples repository](https://github.com/github/platform-samples/blob/master/graphql/queries).
|
||||
有关更多查询示例，请参阅 [platform-samples存储库](https://github.com/github/platform-samples/blob/master/graphql/queries)。
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghec or ghes > 3.2 or ghae-issue-6648 %}
|
||||
## Querying the audit log REST API
|
||||
## 查询审核日志 REST API
|
||||
|
||||
To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log REST API to keep copies of your audit log data and monitor:
|
||||
为确保知识产权得到保护并保持企业的合规，您可以使用审核日志 REST API 保留审核日志数据的副本并监控：
|
||||
{% data reusables.audit_log.audited-data-list %}
|
||||
|
||||
{% data reusables.audit_log.retention-periods %}
|
||||
|
||||
For more information about the audit log REST API, see "[Enterprise administration](/rest/reference/enterprise-admin#audit-log)" and "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)."
|
||||
有关审核日志 REST API 的详细信息，请参阅“[企业管理](/rest/reference/enterprise-admin#audit-log)”和“[组织](/rest/reference/orgs#get-the-audit-log-for-an-organization)”。
|
||||
|
||||
### Example 1: All events in an enterprise, for a specific date, with pagination
|
||||
### 示例 1：企业中特定日期的所有事件，并带有分页
|
||||
|
||||
The query below searches for audit log events created on Jan 1st, 2022 in the `avocado-corp` enterprise, and return the first page with a maximum of 100 items per page using [REST API pagination](/rest/overview/resources-in-the-rest-api#pagination):
|
||||
下面的查询搜索在 `avocado-corp` 企业中搜索 2022 年 1 月 1 日创建的审核日志事件，并使用 [REST API 分页](/rest/overview/resources-in-the-rest-api#pagination)返回第一页，每页最多包含 100 个项：
|
||||
|
||||
```shell
|
||||
curl -H "Authorization: token <em>TOKEN</em>" \
|
||||
@@ -128,11 +128,11 @@ curl -H "Authorization: token <em>TOKEN</em>" \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&page=1&per_page=100"
|
||||
```
|
||||
|
||||
### Example 2: Events for pull requests in an enterprise, for a specific date and actor
|
||||
### 示例 2：企业中特定日期和参与者的拉取请求事件
|
||||
|
||||
You can specify multiple search phrases, such as `created` and `actor`, by separating them in your formed URL with the `+` symbol or ASCII character code `%20`.
|
||||
您可以指定多个搜索短语，例如 `created` 和 `actor`，方法是在形成的 URL 中使用 `+` 符号或 ASCII 字符代码 `%20`分隔这些短语。
|
||||
|
||||
The query below searches for audit log events for pull requests, where the event occurred on or after Jan 1st, 2022 in the `avocado-corp` enterprise, and the action was performed by the `octocat` user:
|
||||
下面的查询搜索拉取请求的审核日志事件，其中事件发生在 `avocado-corp` 企业中的 2022 年 1 月 1 日或之后，并且该操作由 `octocat` 用户执行：
|
||||
|
||||
```shell
|
||||
curl -H "Authorization: token <em>TOKEN</em>" \
|
||||
|
||||
@@ -33,6 +33,13 @@ Before you can enable and configure {% data variables.product.prodname_registry
|
||||
1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string.
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account.
|
||||
Usage of a SAS Token or SAS URL as connection string is not currently supported.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
## Next steps
|
||||
|
||||
@@ -208,7 +208,7 @@ If this parameter is not used, the {% data variables.product.prodname_codeql_wor
|
||||
|
||||
{% data reusables.code-scanning.codeql-languages-bullets %}
|
||||
|
||||
The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
|
||||
The default {% data variables.product.prodname_codeql_workflow %} file contains a matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about matrices, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
{% data reusables.code-scanning.specify-language-to-analyze %}
|
||||
|
||||
|
||||
@@ -68,7 +68,7 @@ If an automatic build of code for a compiled language within your project fails,
|
||||
|
||||
- Remove the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and add specific build steps. For information about editing the workflow, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)." For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
|
||||
|
||||
- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a build matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix.
|
||||
- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix.
|
||||
|
||||
The following extracts from a workflow show how you can use a matrix within the job strategy to specify languages, and then reference each language within the "Initialize {% data variables.product.prodname_codeql %}" step:
|
||||
|
||||
@@ -190,7 +190,7 @@ If you use self-hosted runners to run {% data variables.product.prodname_codeql
|
||||
|
||||
### Use matrix builds to parallelize the analysis
|
||||
|
||||
The default {% data variables.product.prodname_codeql_workflow %} uses a build matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
|
||||
The default {% data variables.product.prodname_codeql_workflow %} uses a matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
|
||||
|
||||
### Reduce the amount of code being analyzed in a single workflow
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ shortTitle: 设置超时
|
||||
|
||||
代码空间将在一段时间不活动后停止运行。 您可以指定此超时期限的长度。 更新后的设置将应用于任何新创建的代码空间。
|
||||
|
||||
Some organizations may have a maximum idle timeout policy. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting, and you will be notified of this after the codespace is created. For more information, see "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
|
||||
某些组织可能有最大空闲超时策略。 如果组织策略设置的最大超时小于您设置的默认超时，则将使用组织的超时而不是您的设置，并且在创建代码空间后，您将收到通知。 更多信息请参阅“[限制空闲超时期限](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)”。
|
||||
|
||||
{% warning %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 限制对计算机类型的访问
|
||||
shortTitle: Restrict machine types
|
||||
shortTitle: 限制机器类型
|
||||
intro: 您可以对用户在组织中创建代码空间时可以选择的计算机类型设置约束。
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
permissions: 'To manage access to machine types for the repositories in an organization, you must be an owner of the organization.'
|
||||
@@ -57,7 +57,7 @@ topics:
|
||||
|
||||
|
||||
{% data reusables.codespaces.codespaces-policy-targets %}
|
||||
1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
|
||||
1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. 有关其他约束的信息，请参阅“[限制转发端口可见性](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)”和“[限制空闲超时期限](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)”。
|
||||
1. After you have finished adding constraints to your policy, click **Save**.
|
||||
## 编辑策略
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 限制转发端口的可见性
|
||||
shortTitle: Restrict port visibility
|
||||
shortTitle: 限制端口可见性
|
||||
intro: 您可以对用户在从组织中的代码空间转发端口时可以选择的可见性选项设置约束。
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an owner of the organization.'
|
||||
@@ -54,7 +54,7 @@ topics:
|
||||
|
||||
|
||||
{% data reusables.codespaces.codespaces-policy-targets %}
|
||||
1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
|
||||
1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. 有关其他约束的信息，请参阅“[限制对计算机类型的访问](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)”和“[限制空闲超时期限](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)”。
|
||||
1. After you have finished adding constraints to your policy, click **Save**.
|
||||
## 编辑策略
|
||||
|
||||
|
||||
@@ -124,10 +124,10 @@ shortTitle: 提交和审核更改
|
||||
|
||||
{% data reusables.desktop.push-origin %}
|
||||
|
||||
6. If you have a pull request based off the branch you are working on, {% data variables.product.prodname_desktop %} will display the status of the checks that have run for the pull request. For more information about checks, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)."
|
||||
6. 如果您有基于正在处理的分支的拉取请求， {% data variables.product.prodname_desktop %} 将显示已为拉取请求运行的检查的状态。 有关检查的详细信息，请参阅“[Viewing and re-running checks in GitHub Desktop（在 GitHub Desktop 中查看和重新运行检查）](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)”。
|
||||
|
||||
|
||||
|
||||
If a pull request has not been created for the current branch, {% data variables.product.prodname_desktop %} will give you the option to create one. For more information, see "[Creating an issue or pull request](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request)."
|
||||
如果尚未为当前分支创建拉取请求，{% data variables.product.prodname_desktop %} 将为您提供创建一个请求的选项。 更多信息请参阅“[创建议题或拉取请求](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request)”。
|
||||
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ versions:
|
||||
|
||||
在 {% data variables.product.prodname_desktop %} 中查看拉取请求时，您可以看到贡献者的提交历史记录。 您还可以查看修改、添加或删除了提交的文件。 从 {% data variables.product.prodname_desktop %} 可以在首选文本编辑器中打开仓库以查看任何更改或进行其他更改。 在审查拉取请求中的更改后，您可以对 {% data variables.product.prodname_dotcom %} 提供反馈。 更多信息请参阅“[关于拉取请求审查](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)”。
|
||||
|
||||
If checks have been enabled in your repository, {% data variables.product.prodname_desktop %} will show the status of the checks on the pull request and allow you to re-run checks. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)."
|
||||
如果存储库中已启用检查，{% data variables.product.prodname_desktop %} 将显示拉取请求上的检查状态，并允许您重新运行检查。 For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)."
|
||||
|
||||
## 在 {% data variables.product.prodname_desktop %} 中查看拉取请求
|
||||
{% data reusables.desktop.current-branch-menu %}
|
||||
|
||||
@@ -67,9 +67,9 @@ X-Accepted-OAuth-Scopes: user
|
||||
|  `user:follow` | 授予关注或取消关注其他用户的权限。 |
|
||||
| **`delete_repo`** | 授予删除可管理仓库的权限。 |
|
||||
| **`write:discussion`** | 授予对团队讨论的读取和写入权限。 |
|
||||
|  `read:discussion` | Allows read access for team discussions. |
|
||||
|  `read:discussion` | 允许对团队讨论进行读取访问。 |
|
||||
| **`write:packages`** | 授予在 {% data variables.product.prodname_registry %} 中上传或发布包的权限。 更多信息请参阅“[发布包](/github/managing-packages-with-github-packages/publishing-a-package)”。 |
|
||||
| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)".{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 更多信息请参阅“[安装包](/github/managing-packages-with-github-packages/installing-a-package)”。{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
| **`delete:packages`** | 授予从 {% data variables.product.prodname_registry %} 删除包的权限。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。{% endif %}
|
||||
| **`admin:gpg_key`** | 全面管理 GPG 密钥。 |
|
||||
|  `write:gpg_key` | 创建、列出和查看 GPG 密钥的详细信息。 |
|
||||
|
||||
@@ -18,7 +18,7 @@ shortTitle: Learning resources
|
||||
---
|
||||
## Using Git
|
||||
|
||||
Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can review the [Git command list](https://git-scm.com/docs) or [Git command lookup reference](http://gitref.org) while using the [Try Git](https://try.github.com) simulator.
|
||||
Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can also review the [Git command list](https://git-scm.com/docs).
|
||||
|
||||
## Using {% data variables.product.product_name %}
|
||||
|
||||
|
||||
@@ -142,7 +142,7 @@ topics:
|
||||
|
||||
最后，添加内置工作流程，以便在将项添加到项目时状态设置为**待办事项** 。
|
||||
|
||||
1. In your project, click {% octicon "workflow" aria-label="the workflow icon" %}.
|
||||
1. 在项目中，单击 {% octicon "workflow" aria-label="the workflow icon" %}。
|
||||
2. 在 **Default workflows（默认工作流程）**下，单击 **Item added to project（已添加到项目的项）**。
|
||||
3. 在 **When（何时）**旁边，确保同时选择 `issues（议题）`和 `pull requests（拉取请求）`。
|
||||
4. 在 **Set（设置）**旁边，选择 **Status:Todo（状态：待办事项）**。
|
||||
|
||||
@@ -23,6 +23,7 @@ permissions: Organization owners can remove members from an organization.
|
||||
**警告：**当您从组织删除成员时：
|
||||
- 付费的许可数不会自动降级。 要在从组织中删除用户后减少付费的许可数，请按照“[降级组织的付费席位](/articles/downgrading-your-organization-s-paid-seats)”中的步骤操作。
|
||||
- 被删除的成员将无法访问组织私有仓库的私人复刻，但仍可拥有本地副本。 但是，它们无法将本地副本与组织的仓库同步。 如果用户在从组织中删除后的三个月内[恢复为组织成员](/articles/reinstating-a-former-member-of-your-organization)，则可以恢复其私人复刻。 最终，您负责确保无法访问仓库的人员删除任何机密信息或知识产权。
|
||||
- When private repositories are forked to other organizations, those organizations are able to control access to the fork network. This means users may retain access to the forks even after losing access to the original organization because they will still have explicit access via a fork.
|
||||
{%- ifversion ghec %}
|
||||
- 如果被删除成员不是同一企业帐户拥有的任何其他组织的成员，则被删除成员也将失去对组织内部仓库私人复刻的访问权限。 更多信息请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。
|
||||
{%- endif %}
|
||||
|
||||
@@ -14,12 +14,6 @@ sections:
|
||||
- When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list.
|
||||
- The `/stafftools/users/ip_addresses/:address` page responded with a `500 Internal Server Error` when attempting to display the page for an IPv6 address.
|
||||
- Creating an impersonation OAuth token using the Enterprise Administration REST API resulted in an error when an integration matching the OAuth Application ID already existed.
|
||||
- |
|
||||
When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11]
|
||||
|
||||
To work around this problem, you can take one of the two following actions.
|
||||
- Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute.
|
||||
- Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL.
|
||||
changes:
|
||||
- Added support for replica domain names that are more than 63 characters.
|
||||
- Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log.
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
A matrix strategy lets you use variables in a single job definition to automatically create multiple job runs that are based the combinations of the variables. For example, you can use a matrix strategy to test your code in multiple versions of a language or on multiple operating systems.
|
||||
@@ -0,0 +1,29 @@
|
||||
For example, this matrix will run 10 jobs, one for each combination of `os` and `version` in the matrix, plus a job for the `os` value of `windows-latest` and `version` value of `17`.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
os: [macos-latest, windows-latest, ubuntu-latest]
|
||||
version: [12, 14, 16]
|
||||
include:
|
||||
- os: windows-latest
|
||||
version: 17
|
||||
```
|
||||
|
||||
If you don't specify any matrix variables, all configurations under `include` will run. For example, the following workflow would run two jobs, one for each `include` entry. This lets you take advantage of the matrix strategy without having a fully populated matrix.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
includes_only:
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
include:
|
||||
- site: "production"
|
||||
datacenter: "site-a"
|
||||
- site: "staging"
|
||||
datacenter: "site-b"
|
||||
|
||||
```
|
||||
@@ -0,0 +1,22 @@
|
||||
To remove specific configurations defined in the matrix, use `jobs.<job_id>.strategy.matrix.exclude`. An excluded configuration only has to be a partial match for it to be excluded. For example, the following workflow will run nine jobs: one job for each of the 12 configurations, minus the one excluded job that matches `{os: macos-latest, version: 12, environment: production}`, and the two excluded jobs that match `{os: windows-latest, version: 16}`.
|
||||
|
||||
```yaml
|
||||
strategy:
|
||||
matrix:
|
||||
os: [macos-latest, windows-latest]
|
||||
version: [12, 14, 16]
|
||||
environment: [staging, production]
|
||||
exclude:
|
||||
- os: macos-latest
|
||||
version: 12
|
||||
environment: production
|
||||
- os: windows-latest
|
||||
version: 16
|
||||
runs-on: {% raw %}${{ matrix.os }}{% endraw %}
|
||||
```
|
||||
|
||||
{% note %}
|
||||
|
||||
**注意：**所有 `include` 组合在 `exclude` 后处理。 这允许您使用 `include` 添加回以前排除的组合。
|
||||
|
||||
{% endnote %}
|
||||
@@ -0,0 +1,22 @@
|
||||
For example, the following workflow will run six jobs, one for each combination of `os` and `node`. When the job for the `os` value of `windows-latest` and `node` value of `16` runs, an additional variable called `npm` with the value of `6` will be included in the job.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
os: [windows-latest, ubuntu-latest]
|
||||
node: [12, 14, 16]
|
||||
include:
|
||||
- os: windows-latest
|
||||
node: 16
|
||||
npm: 6
|
||||
runs-on: {% raw %}${{ matrix.os }}{% endraw %}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.node }}{% endraw %}
|
||||
- if: {% raw %}${{ matrix.npm }}{% endraw %}
|
||||
run: npm install -g npm@{% raw %}${{ matrix.npm }}{% endraw %}
|
||||
- run: npm --version
|
||||
```
|
||||
@@ -0,0 +1,30 @@
|
||||
You can use contexts to create matrices. 有关上下文的更多信息，请参阅“[上下文](/actions/learn-github-actions/contexts)”。
|
||||
|
||||
For example, the following workflow triggers on the `repository_dispatch` event and uses information from the event payload to build the matrix. When a repository dispatch event is created with a payload like the one below, the matrix `version` variable will have a value of `[12, 14, 16]`. For more information about the `repository_dispatch` trigger, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows#repository_dispatch)."
|
||||
|
||||
```json
|
||||
{
|
||||
"event_type": "test",
|
||||
"client_payload": {
|
||||
"versions": [12, 14, 16]
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
```yaml
|
||||
on:
|
||||
repository_dispatch:
|
||||
types:
|
||||
- test
|
||||
|
||||
jobs:
|
||||
example_matrix:
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
version: {% raw %}${{ github.event.client_payload.versions }}{% endraw %}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.version }}{% endraw %}
|
||||
```
|
||||
@@ -0,0 +1,38 @@
|
||||
Use `jobs.<job_id>.strategy.matrix.include` to expand existing matrix configurations or to add new configurations. The value of `include` is a list of objects.
|
||||
|
||||
For each object in the `include` list, the key:value pairs in the object will be added to each of the matrix combinations if none of the key:value pairs overwrite any of the original matrix values. If the object cannot be added to any of the matrix combinations, a new matrix combination will be created instead. Note that the original matrix values will not be overwritten, but added matrix values can be overwritten.
|
||||
|
||||
For example, this matrix:
|
||||
|
||||
```yaml
|
||||
strategy:
|
||||
matrix:
|
||||
fruit: [apple, pear]
|
||||
animal: [cat, dog]
|
||||
include:
|
||||
- color: green
|
||||
- color: pink
|
||||
animal: cat
|
||||
- fruit: apple
|
||||
shape: circle
|
||||
- fruit: banana
|
||||
- fruit: banana
|
||||
animal: cat
|
||||
```
|
||||
|
||||
will result in six jobs with the following matrix combinations:
|
||||
|
||||
- `{fruit: apple, animal: cat, color: pink, shape: circle}`
|
||||
- `{fruit: apple, animal: dog, color: green, shape: circle}`
|
||||
- `{fruit: pear, animal: cat, color: pink}`
|
||||
- `{fruit: pear, animal: dog, color: green}`
|
||||
- `{fruit: banana}`
|
||||
- `{fruit: banana, animal: cat}`
|
||||
|
||||
following this logic:
|
||||
|
||||
- `{color: green}` is added to all of the original matrix combinations because it can be added without overwriting any part of the original combinations.
|
||||
- `{color: pink, animal: cat}` adds `color:pink` only to the original matrix combinations that include `animal: cat`. This overwrites the `color: green` that was added by the previous `include` entry.
|
||||
- `{fruit: apple, shape: circle}` adds `shape: circle` only to the original matrix combinations that include `fruit: apple`.
|
||||
- `{fruit: banana}` cannot be added to any original matrix combination without overwriting a value, so it is added as an additional matrix combination.
|
||||
- `{fruit: banana, animal: cat}` cannot be added to any original matrix combination without overwriting a value, so it is added as an additional matrix combination. It does not add to the `{fruit: banana}` matrix combination because that combination was not one of the original matrix combinations.
|
||||
@@ -0,0 +1,22 @@
|
||||
You can specify multiple variables to create a multi-dimensional matrix. A job will run for each possible combination of the variables.
|
||||
|
||||
For example, the following workflow specifies two variables:
|
||||
|
||||
- Two operating systems specified in the `os` variable
|
||||
- Three Node.js versions specified in the `version` variable
|
||||
|
||||
The workflow will run six jobs, one for each combination of the `os` and `version` variables. Each job will set the `runs-on` value to the current `os` value and will pass the current `version` value to the `actions/setup-node` action.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
os: [ubuntu-18.04, ubuntu-20.04]
|
||||
version: [10, 12, 14]
|
||||
runs-on: {% raw %}${{ matrix.os }}{% endraw %}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.version }}{% endraw %}
|
||||
```
|
||||
@@ -1 +1,23 @@
|
||||
When `jobs.<job_id>.strategy.fail-fast` is set to `true`, {% data variables.product.prodname_dotcom %} cancels all in-progress jobs in the matrix if any `matrix` job fails. 默认值：`true`
|
||||
You can control how job failures are handled with `jobs.<job_id>.strategy.fail-fast` and `jobs.<job_id>.continue-on-error`.
|
||||
|
||||
`jobs.<job_id>.strategy.fail-fast` applies to the entire matrix. If `jobs.<job_id>.strategy.fail-fast` is set to `true`, {% data variables.product.product_name %} will cancel all in-progress and queued jobs in the matrix if any job in the matrix fails. This property defaults to `true`.
|
||||
|
||||
`jobs.<job_id>.continue-on-error` applies to a single job. If `jobs.<job_id>.continue-on-error` is `true`, other jobs in the matrix will continue running even if the job with `jobs.<job_id>.continue-on-error: true` fails.
|
||||
|
||||
You can use `jobs.<job_id>.strategy.fail-fast` and `jobs.<job_id>.continue-on-error` together. For example, the following workflow will start four jobs. For each job, `continue-on-error` is determined by the value of `matrix.experimental`. If any of the jobs with `continue-on-error: false` fail, all jobs that are in progress or queued will be cancelled. If the job with `continue-on-error: true` fails, the other jobs will not be affected.
|
||||
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
test:
|
||||
runs-on: ubuntu-latest
|
||||
continue-on-error: {% raw %}${{ matrix.experimental }}{% endraw %}
|
||||
strategy:
|
||||
fail-fast: true
|
||||
matrix:
|
||||
version: [6, 7, 8]
|
||||
experimental: [false]
|
||||
include:
|
||||
- version: 9
|
||||
experimental: true
|
||||
```
|
||||
|
||||
@@ -1,122 +0,0 @@
|
||||
|
||||
Use `jobs.<job_id>.strategy.matrix` to define a matrix of different job configurations. 矩阵允许您通过在单个作业定义中执行变量替换来创建多个作业。 例如，可以使用矩阵为多个受支持的编程语言、操作系统或工具版本创建作业。 矩阵重新使用作业的配置，并为您配置的每个矩阵创建作业。
|
||||
|
||||
{% data reusables.actions.usage-matrix-limits %}
|
||||
|
||||
您在 `matrix` 中定义的每个选项都有键和值。 定义的键将成为 `matrix` 上下文中的属性，您可以在工作流程文件的其他区域中引用该属性。 例如，如果定义包含操作系统数组的键 `os`，您可以使用 `matrix.os` 属性作为 `runs-on` 关键字的值，为每个操作系统创建一个作业。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。
|
||||
|
||||
定义 `matrix` 事项的顺序。 定义的第一个选项将是工作流程中运行的第一个作业。
|
||||
|
||||
#### 示例：运行多个版本的 Node.js
|
||||
|
||||
您可以提供配置选项阵列来指定矩阵。 例如，如果运行器支持 Node.js 版本 10、12 和 14，则您可以在 `matrix` 中指定这些版本的阵列。
|
||||
|
||||
此示例通过设置三个 Node.js 版本阵列的 `node` 键创建三个作业的矩阵。 为使用矩阵，示例将 `matrix.node` 上下文属性设置为 `setup-node` 操作的输入参数 `node-version`。 因此，将有三个作业运行，每个使用不同的 Node.js 版本。
|
||||
|
||||
```yaml
|
||||
strategy:
|
||||
matrix:
|
||||
node: [10, 12, 14]
|
||||
steps:
|
||||
# Configures the node version used on GitHub-hosted runners
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
# The Node.js version to configure
|
||||
node-version: {% raw %}${{ matrix.node }}{% endraw %}
|
||||
```
|
||||
|
||||
`setup-node` 操作是在使用 {% data variables.product.prodname_dotcom %} 托管的运行器时建议用于配置 Node.js 版本的方式。 更多信息请参阅 [`setup-node`](https://github.com/actions/setup-node) 操作。
|
||||
|
||||
#### 示例：使用多个操作系统运行
|
||||
|
||||
您可以创建矩阵以在多个运行器操作系统上运行工作流程。 您也可以指定多个矩阵配置。 此示例创建包含 6 个作业的矩阵：
|
||||
|
||||
- 在 `os` 阵列中指定了 2 个操作系统
|
||||
- 在 `node` 阵列中指定了 3 个 Node.js 版本
|
||||
|
||||
{% data reusables.repositories.actions-matrix-builds-os %}
|
||||
|
||||
```yaml
|
||||
runs-on: {% raw %}${{ matrix.os }}{% endraw %}
|
||||
strategy:
|
||||
matrix:
|
||||
os: [ubuntu-18.04, ubuntu-20.04]
|
||||
node: [10, 12, 14]
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.node }}{% endraw %}
|
||||
```
|
||||
|
||||
{% ifversion ghae %}
|
||||
For more information about the configuration of self-hosted runners, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
|
||||
{% else %}要查找 {% data variables.product.prodname_dotcom %} 托管的运行器支持的配置选项，请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器的虚拟环境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)”。
|
||||
{% endif %}
|
||||
|
||||
#### Example: Including additional values in combinations
|
||||
|
||||
您可以将额外的配置选项添加到已经存在的构建矩阵作业中。 例如，如果要在作业使用 `windows-latest` 和 `node` 的版本 8 运行时使用 `npm` 的特定版本，您可以使用 `include` 指定该附加选项。
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
runs-on: ${{ matrix.os }}
|
||||
strategy:
|
||||
matrix:
|
||||
os: [macos-latest, windows-latest, ubuntu-18.04]
|
||||
node: [8, 10, 12, 14]
|
||||
include:
|
||||
# includes a new variable of npm with a value of 6
|
||||
# for the matrix leg matching the os and version
|
||||
- os: windows-latest
|
||||
node: 8
|
||||
npm: 6
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
#### 示例：包括新组合
|
||||
|
||||
您可以使用 `include` 将新作业添加到构建矩阵中。 任何不匹配包含配置都会添加到矩阵中。 例如，如果您想要使用 `node` 版本 14 在多个操作系统上构建，但在 Ubuntu 上需要一个使用节点版本 15 的额外实验性作业，则可使用 `include` 指定该额外作业。
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
runs-on: ${{ matrix.os }}
|
||||
strategy:
|
||||
matrix:
|
||||
node: [14]
|
||||
os: [macos-latest, windows-latest, ubuntu-18.04]
|
||||
include:
|
||||
- node: 15
|
||||
os: ubuntu-18.04
|
||||
experimental: true
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
#### 示例：从矩阵中排除配置
|
||||
|
||||
您可以使用 `exclude` 选项删除构建矩阵中定义的特定配置。 使用 `exclude` 删除由构建矩阵定义的作业。 作业数量是您提供的数组中所包括的操作系统 (`os`) 数量减去所有减项 (`exclude`) 后的叉积。
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
runs-on: ${{ matrix.os }}
|
||||
strategy:
|
||||
matrix:
|
||||
os: [macos-latest, windows-latest, ubuntu-18.04]
|
||||
node: [8, 10, 12, 14]
|
||||
exclude:
|
||||
# excludes node 8 on macOS
|
||||
- os: macos-latest
|
||||
node: 8
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**注意：**所有 `include` 组合在 `exclude` 后处理。 这允许您使用 `include` 添加回以前排除的组合。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### 在矩阵中使用环境变量
|
||||
|
||||
您可以使用 `include` 键为每个测试组合添加自定义环境变量。 然后，您可以在后面的步骤中引用自定义环境变量。
|
||||
|
||||
{% data reusables.actions.matrix-variable-example %}
|
||||
@@ -1,6 +1,13 @@
|
||||
Use `jobs.<job_id>.strategy.max-parallel` to set the maximum number of jobs that can run simultaneously when using a `matrix` job strategy. 默认情况下，{% data variables.product.prodname_dotcom %} 将最大化并发运行的作业数量，具体取决于 {% data variables.product.prodname_dotcom %} 托管虚拟机上可用的运行程序。
|
||||
By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. To set the maximum number of jobs that can run simultaneously when using a `matrix` job strategy, use `jobs.<job_id>.strategy.max-parallel`.
|
||||
|
||||
For example, the following workflow will run a maximum of two jobs at a time, even if there are runners available to run all six jobs at once.
|
||||
|
||||
```yaml
|
||||
strategy:
|
||||
max-parallel: 2
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
max-parallel: 2
|
||||
matrix:
|
||||
version: [10, 12, 14]
|
||||
os: [ubuntu-latest, windows-latest]
|
||||
```
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
Use `jobs.<job_id>.strategy` to create a build matrix for your jobs. 您可以定义要在其中运行每项作业的不同变种。
|
||||
@@ -0,0 +1,15 @@
|
||||
You can specify a single variable to create a single-dimension matrix.
|
||||
|
||||
For example, the following workflow defines the variable `version` with the values `[10, 12, 14]`. The workflow will run three jobs, one for each value in the variable. Each job will access the `version` value through the `matrix.version` context and pass the value as `node-version` to the `actions/setup-node` action.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
version: [10, 12, 14]
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.version }}{% endraw %}
|
||||
```
|
||||
@@ -0,0 +1,25 @@
|
||||
Use `jobs.<job_id>.strategy.matrix` to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a veriable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`:
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
version: [10, 12, 14]
|
||||
os: [ubuntu-latest, windows-latest]
|
||||
```
|
||||
|
||||
A job will run for each possible combination of the variables. In this example, the workflow will run six jobs, one for each combination of the `os` and `version` variables.
|
||||
|
||||
By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. The order of the variables in the matrix determines the order in which the jobs are created. The first variable you define will be the first job that is created in your workflow run. For example, the above matrix will create the jobs in the following order:
|
||||
|
||||
- `{version: 10, os: ubuntu-latest}`
|
||||
- `{version: 10, os: windows-latest}`
|
||||
- `{version: 12, os: ubuntu-latest}`
|
||||
- `{version: 12, os: windows-latest}`
|
||||
- `{version: 14, os: ubuntu-latest}`
|
||||
- `{version: 14, os: windows-latest}`
|
||||
|
||||
A matrix will generate a maximum of 256 jobs per workflow run. This limit applies to both {% data variables.product.product_name %}-hosted and self-hosted runners.
|
||||
|
||||
The variables that you define become properties in the `matrix` context, and you can reference the property in other areas of your workflow file. In this example, you can use `matrix.version` and `matrix.os` to access the current value of `version` and `os` that the job is using. 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。
|
||||
@@ -1 +0,0 @@
|
||||
定义操作系统矩阵时，必须将 `runs-on` 的值设置为您定义的 `matrix.os` 上下文属性。
|
||||
@@ -9,9 +9,9 @@ Adobe | Adobe Service Token | adobe_service_token{% endif %}
|
||||
Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Amazon | Amazon OAuth Client ID | amazon_oauth_client_id{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Amazon | Amazon OAuth Client Secret | amazon_oauth_client_secret{% endif %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %}
|
||||
@@ -21,9 +21,9 @@ Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_a
|
||||
Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} Atlassian | Atlassian API Token | atlassian_api_token Atlassian | Atlassian JSON Web Token | atlassian_jwt
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key{% endif %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token Azure | Azure SAS Token | azure_sas_token Azure | Azure Service Management Certificate | azure_management_certificate
|
||||
{%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %}
|
||||
Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} Azure | Azure Storage Account Key | azure_storage_account_key
|
||||
@@ -63,7 +63,7 @@ GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %}
|
||||
GitHub | GitHub Refresh Token | github_refresh_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} GitHub | GitHub SSH Private Key | github_ssh_private_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
GitLab | GitLab Access Token | gitlab_access_token{% endif %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} Google | Google API Key | google_api_key Google | Google Cloud Private Key ID | google_cloud_private_key_id
|
||||
@@ -73,13 +73,13 @@ Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_ke
|
||||
Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Google | Google OAuth Access Token | google_oauth_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Google | Google OAuth Client ID | google_oauth_client_id{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Google | Google OAuth Client Secret | google_oauth_client_secret{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Grafana | Grafana API Key | grafana_api_key{% endif %} HashiCorp | Terraform Cloud / Enterprise API Token | terraform_api_token HashiCorp | HashiCorp Vault Batch Token | hashicorp_vault_batch_token HashiCorp | HashiCorp Vault Service Token | hashicorp_vault_service_token Hubspot | Hubspot API Key | hubspot_api_key
|
||||
@@ -89,7 +89,7 @@ Intercom | Intercom Access Token | intercom_access_token{% endif %}
|
||||
Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
JD Cloud | JD Cloud Access Key | jd_cloud_access_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %}
|
||||
@@ -103,15 +103,15 @@ Linear | Linear OAuth Access Token | linear_oauth_access_token{% endif %}
|
||||
Lob | Lob Live API Key | lob_live_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Lob | Lob Test API Key | lob_test_api_key{% endif %} Mailchimp | Mailchimp API Key | mailchimp_api_key Mailgun | Mailgun API Key | mailgun_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Mapbox | Mapbox Secret Access Token | mapbox_secret_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
MessageBird | MessageBird API Key | messagebird_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Meta | Facebook Access Token | facebook_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Midtrans | Midtrans Production Server Key | midtrans_production_server_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %}
|
||||
@@ -121,11 +121,11 @@ New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %}
|
||||
New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
New Relic | New Relic License Key | new_relic_license_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Notion | Notion Integration Token | notion_integration_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Notion | Notion OAuth Client Secret | notion_oauth_client_secret{% endif %} npm | npm Access Token | npm_access_token NuGet | NuGet API Key | nuget_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Octopus Deploy | Octopus Deploy API Key | octopus_deploy_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Onfido | Onfido Live API Token | onfido_live_api_token{% endif %}
|
||||
@@ -147,7 +147,7 @@ Plivo | Plivo Auth Token | plivo_auth_token{% endif %} Postman | Postman API Key
|
||||
PyPI | PyPI API Token | pypi_api_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
RubyGems | RubyGems API Key | rubygems_api_key{% endif %} Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
Segment | Segment Public API Token | segment_public_api_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
SendGrid | SendGrid API Key | sendgrid_api_key{% endif %}
|
||||
@@ -159,36 +159,36 @@ Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %}
|
||||
Shippo | Shippo Live API Token | shippo_live_api_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Shippo | Shippo Test API Token | shippo_test_api_token{% endif %} Shopify | Shopify App Shared Secret | shopify_app_shared_secret Shopify | Shopify Access Token | shopify_access_token Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token Shopify | Shopify Private App Password | shopify_private_app_password Slack | Slack API Token | slack_api_token Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Square | Square Access Token | square_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Square | Square Production Application Secret | square_production_application_secret{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Square | Square Sandbox Application Secret | square_sandbox_application_secret{% endif %} SSLMate | SSLMate API Key | sslmate_api_key SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret Stripe | Stripe API Key | stripe_api_key Stripe | Stripe Live API Secret Key | stripe_live_secret_key Stripe | Stripe Test API Secret Key | stripe_test_secret_key Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Supabase | Supabase Service Key | supabase_service_key{% endif %} Tableau | Tableau Personal Access Token | tableau_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Telegram | Telegram Bot Token | telegram_bot_token{% endif %} Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Twilio | Twilio Access Token | twilio_access_token{% endif %} Twilio | Twilio Account String Identifier | twilio_account_sid Twilio | Twilio API Key | twilio_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Typeform | Typeform Personal Access Token | typeform_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
WorkOS | WorkOS Production API Key | workos_production_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
WorkOS | WorkOS Staging API Key | workos_staging_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Yandex.Cloud API Key | yandex_cloud_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Yandex.Cloud IAM Cookie | yandex_cloud_iam_cookie{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Yandex.Cloud IAM Token | yandex_cloud_iam_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Yandex.Dictionary API Key | yandex_dictionary_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Yandex.Predictor API Key | yandex_predictor_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Yandex.Translate API Key | yandex_translate_api_key{% endif %}
|
||||
|
||||
Reference in New Issue
Block a user