From db6cbe236ee73ad7bcefa9a82e53f1a8e82b425c Mon Sep 17 00:00:00 2001 From: Berenice Monsivais <153947742+beremonsivais@users.noreply.github.com> Date: Thu, 5 Sep 2024 20:59:35 -0600 Subject: [PATCH 1/2] Fixes github/docs#33389 A note is added to clarify when the configuration variables at the environment level are automatically available. --- .../accessing-contextual-information-about-workflow-runs.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md b/content/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md index ff2544a3bb48..d676d15a9b56 100644 --- a/content/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md +++ b/content/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md @@ -365,6 +365,9 @@ The contents of the `vars` context is a mapping of configuration variable names This example workflow shows how configuration variables set at the repository, environment, or organization levels are automatically available using the `vars` context. +> [!NOTE] +> Configuration variables at the environment level are automatically available after their environment is declared by the runner. + {% data reusables.actions.actions-vars-context-example-usage %} ## `job` context From 58d65e9144a592908626cc70cf289ead09b71572 Mon Sep 17 00:00:00 2001 From: Berenice Monsivais <153947742+beremonsivais@users.noreply.github.com> Date: Fri, 6 Sep 2024 10:12:13 -0600 Subject: [PATCH 2/2] Added format to new note Fixes github/docs #33389 Added correct format to new note. --- ...accessing-contextual-information-about-workflow-runs.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/content/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md b/content/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md index d676d15a9b56..a9855f035f2d 100644 --- a/content/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md +++ b/content/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md @@ -365,8 +365,11 @@ The contents of the `vars` context is a mapping of configuration variable names This example workflow shows how configuration variables set at the repository, environment, or organization levels are automatically available using the `vars` context. -> [!NOTE] -> Configuration variables at the environment level are automatically available after their environment is declared by the runner. +{% note %} + +Note: Configuration variables at the environment level are automatically available after their environment is declared by the runner. + +{% endnote %} {% data reusables.actions.actions-vars-context-example-usage %}