Skip to content

Commit f9f3e19

Browse files
authored
Note that matrix variable names are case insensitive
1 parent c574b79 commit f9f3e19

3 files changed

Lines changed: 6 additions & 0 deletions

File tree

‎content/actions/reference/workflows-and-actions/contexts.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -730,6 +730,8 @@ There are no standard properties in the `matrix` context, only those which are d
730730
| `matrix` | `object` | This context is only available for jobs in a matrix, and changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains the properties listed below. |
731731
| `matrix.<property_name>` | `string` | The value of a matrix property. |
732732

733+
{% data reusables.actions.workflows.matrix-keys-are-case-insensitive %}
734+
733735
### Example contents of the `matrix` context
734736

735737
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. The job is executing the matrix combination of an `ubuntu-latest` OS and Node.js version `16`.

‎content/actions/reference/workflows-and-actions/workflow-syntax.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1242,6 +1242,8 @@ A matrix will generate a maximum of 256 jobs per workflow run. This limit applie
12421242

12431243
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. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/contexts).
12441244

1245+
{% data reusables.actions.workflows.matrix-keys-are-case-insensitive %}
1246+
12451247
By default, {% data variables.product.github %} 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.
12461248

12471249
### Using a single-dimension matrix
Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
> [!NOTE]
2+
> * The variable names are case insensitive. For example, `OS` and `os` will be treated as the same variable.

0 commit comments

Comments
 (0)