jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-20 10:28:40 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #34367 from github/repo-sync

Browse Source 
repo sync
This commit is contained in:
Octomerger Bot
2023-02-02 01:05:38 -08:00
committed by GitHub
parent 6855ccc37b 9f2d467098
commit d09e48e2fc
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/actions/learn-github-actions/variables.md
View File

@@ -54,7 +54,7 @@ To set a custom environment variable{% ifversion actions-configuration-variables
* A specific step within a job, by using [`jobs.<job_id>.steps[*].env`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsenv). * A specific step within a job, by using [`jobs.<job_id>.steps[*].env`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsenv).
{% raw %} {% raw %}
```yaml ```yaml{:copy}
name: Greeting on variable day name: Greeting on variable day
on: on:
@@ -184,7 +184,7 @@ In addition to runner environment variables, {% data variables.product.prodname_
Runner environment variables are always interpolated on the runner machine. However, parts of a workflow are processed by {% data variables.product.prodname_actions %} and are not sent to the runner. You cannot use environment variables in these parts of a workflow file. Instead, you can use contexts. For example, an `if` conditional, which determines whether a job or step is sent to the runner, is always processed by {% data variables.product.prodname_actions %}. You can use a context in an `if` conditional statement to access the value of an variable. Runner environment variables are always interpolated on the runner machine. However, parts of a workflow are processed by {% data variables.product.prodname_actions %} and are not sent to the runner. You cannot use environment variables in these parts of a workflow file. Instead, you can use contexts. For example, an `if` conditional, which determines whether a job or step is sent to the runner, is always processed by {% data variables.product.prodname_actions %}. You can use a context in an `if` conditional statement to access the value of an variable.
{% raw %} {% raw %}
```yaml ```yaml{:copy}
env: env:
DAY_OF_WEEK: Monday DAY_OF_WEEK: Monday
@@ -308,7 +308,7 @@ We strongly recommend that actions use variables to access the filesystem rather
You can write a single workflow file that can be used for different operating systems by using the `RUNNER_OS` default environment variable and the corresponding context property <span style="white-space: nowrap;">{% raw %}`${{ runner.os }}`{% endraw %}</span>. For example, the following workflow could be run successfully if you changed the operating system from `macos-latest` to `windows-latest` without having to alter the syntax of the environment variables, which differs depending on the shell being used by the runner. You can write a single workflow file that can be used for different operating systems by using the `RUNNER_OS` default environment variable and the corresponding context property <span style="white-space: nowrap;">{% raw %}`${{ runner.os }}`{% endraw %}</span>. For example, the following workflow could be run successfully if you changed the operating system from `macos-latest` to `windows-latest` without having to alter the syntax of the environment variables, which differs depending on the shell being used by the runner.
{% raw %} {% raw %}
```yaml ```yaml{:copy}
jobs: jobs:
if-Windows-else: if-Windows-else:
runs-on: macos-latest runs-on: macos-latest

2
data/reusables/actions/actions-vars-context-example-usage.md
View File

@@ -4,7 +4,7 @@ The following example shows using configuration variables with the `vars` contex
{% raw %} {% raw %}
```yaml ```yaml{:copy}
on: on:
workflow_dispatch: workflow_dispatch:
env: env: